DTLoggedExec Release Rss Feed

Updated Release: 1.1.2008.4 SP2 (Feb 01, 2012)

manowar — Wed, 01 Feb 2012 17:15:41 GMT

Notes
This SP2 release add an important feature to the CSV Log Provider. It's now possible to store a personalized label into each log, in order to make it easy to identify or group logs.

Let's say, for example, that you have 10 packages in your ETL solution, and each time you have to load your data, you need to execute all those 10 packages. In other words , you have a batch made of 10 packages. It would be nice if all logs - one for each package - can be identified as a whole and grouped together, in order to quickly identify all the log of a articular batch.

This will make things easier when you want to know the overal time consumed by each batch execution.

The new "ExecutionLabel" attribute will help to achieve this. A useful ExecutionLabel can be obtained using SQL Server Agents Token. For example:

LABEL=$(ESCAPE_SQUOTE(JOBID))_$(ESCAPE_SQUOTE(STRTDT))_$(ESCAPE_SQUOTE(STRTTM))

ChangeLog

Updated the CSV Log Provider in order to write the status of the log file in the header.
- An OPEN status means that the log file is being written.
- A CLOSED status means that the log files has been written correctly.
- A file can be loaded into the database log only if is in the CLOSED state.
CSV Log files have 2 additional rows in the header: one for the FileStatus and one for the ExecutionLabel values.
- File format has been update to 4 from 3. (Only the header section of the file has been changed).
CSV Log Provider will now display EndTime value to the Console
Updated the import-log-data.sql to correctly load file with format 3 (the old one) and 4 (the new one).
Updated database schema to version 19 in order to store the new ExecutionLabel value
Update samples in order to show how to use the new ExecuteLabel option

Released: 1.1.2008.4 SP2 (Feb 01, 2012)

Wed, 01 Feb 2012 17:15:41 GMT

Updated the CSV Log Provider in order to write the status of the log file in the header.
- An OPEN status means that the log file is being written.
- A CLOSED status means that the log files has been written correctly.
- A file can be loaded into the database log only if is in the CLOSED state.
CSV Log files have 2 additional rows in the header: one for the FileStatus and one for the ExecutionLabel values.
- File format has been update to 4 from 3. (Only the header section of the file has been changed).
CSV Log Provider will now display EndTime value to the Console
Updated the import-log-data.sql to correctly load file with format 3 (the old one) and 4 (the new one).
Updated database schema to version 19 in order to store the new ExecutionLabel value
Update samples in order to show how to use the new ExecuteLabel option

Updated Release: 1.1.2008.4 SP2 (Feb 01, 2012)

manowar — Wed, 01 Feb 2012 17:13:56 GMT

Notes
This SP2 release add an important feature to the CSV Log Provider. It's now possible to store a personalized label into each log, in order to make it easy to identify or group logs.

Let's say, for example, that you have 10 packages in your ETL solution, and each time you have to load your data, you need to execute all those 10 packages. In other words , you have a batch made of 10 packages. It would be nice if all logs - one for each package - can be identified as a whole and grouped together, in order to quickly identify all the log of a articular batch.

The new "ExecutionLabel" attribute will help to achieve this. A useful ExecutionLabel can be obtained using SQL Server Agents Token. For example:

LABEL=$(ESCAPE_SQUOTE(JOBID))_$(ESCAPE_SQUOTE(STRTDT))_$(ESCAPE_SQUOTE(STRTTM))

ChangeLog

Updated the CSV Log Provider in order to write the status of the log file in the header.
- An OPEN status means that the log file is being written.
- A CLOSED status means that the log files has been written correctly.
- A file can be loaded into the database log only if is in the CLOSED state.
CSV Log files have 2 additional rows in the header: one for the FileStatus and one for the ExecutionLabel values.
- File format has been update to 4 from 3. (Only the header section of the file has been changed).
CSV Log Provider will now display EndTime value to the Console
Updated the import-log-data.sql to correctly load file with format 3 (the old one) and 4 (the new one).
Updated database schema to version 19 in order to store the new ExecutionLabel value
Update samples in order to show how to use the new ExecuteLabel option

Updated Release: 1.1.2008.4 SP2 (Feb 01, 2012)

manowar — Wed, 01 Feb 2012 17:12:05 GMT

Notes
This SP2 release add an important feature to the CSV Log Provider. It's now possibile to store a personalized label into each log, in order to make it easy to identify or group log.
Let's say, for example, that you have 10 packages in your ETL solution, and each time you have to load your data, you need to execute all those 10 packages. In other words, you have a batch made of 10 packages. It would be nice if all logs - one for each package - can be identfied as a whole and grouped togheter, in order to quickly identify all the log of a articular batch. The new "ExecutionLabel" attribute will help to achieve this.

A useful ExecutionLabel can be obtained using SQL Server Agents Token. For example:
LABEL=$(ESCAPE_SQUOTE(JOBID))_$(ESCAPE_SQUOTE(STRTDT))_$(ESCAPE_SQUOTE(STRTTM))

ChangeLog

Updated the CSV Log Provider in order to write the status of the log file in the header.
- An OPEN status means that the log file is being written.
- A CLOSED status means that the log files has been written correctly.
- A file can be loaded into the database log only if is in the CLOSED state.
CSV Log files have 2 additional rows in the header: one for the FileStatus and one for the ExecutionLabel values.
- File format has been update to 4 from 3. (Only the header section of the file has been changed).
CSV Log Provider will now display EndTime value to the Console
Updated the import-log-data.sql to correctly load file with format 3 (the old one) and 4 (the new one).
Updated database schema to version 19 in order to store the new ExecutionLabel value

Updated Release: 1.1.2008.4 SP2 (Feb 01, 2012)

manowar — Wed, 01 Feb 2012 15:23:24 GMT

Notes
This SP2 release add an important feature to the CSV Log Provider. It's now possibile to store a personalized label into each log, in order to make it easy to identify or group log.
Let's say, for example, that you have 10 packages in your ETL solution, and each time you have to load your data, you need to execute all those 10 packages. In order orders, you have a batch made of 10 packages. It would be nice if all logs - one for each package - can be identfied as a whole and grouped togheter, in order to quickly identify all the log of a articular batch. The new "ExecutionLabel" attribute will help to achieve this.

A useful ExecutionLabel can be obtained using SQL Server Agents Token. For example:
LABEL=$(ESCAPE_SQUOTE(JOBID))_$(ESCAPE_SQUOTE(STRTDT))_$(ESCAPE_SQUOTE(STRTTM))

ChangeLog

Updated the CSV Log Provider in order to write the status of the log file in the header.
- An OPEN status means that the log file is being written.
- A CLOSED status means that the log files has been written correctly.
- A file can be loaded into the database log only if is in the CLOSED state.
CSV Log files have 2 additional rows in the header: one for the FileStatus and one for the ExecutionLabel values.
- File format has been update to 4 from 3. (Only the header section of the file has been changed).
CSV Log Provider will now display EndTime value to the Console
Updated the import-log-data.sql to correctly load file with format 3 (the old one) and 4 (the new one).
Updated database schema to version 19 in order to store the new ExecutionLabel value

Released: 1.1.2008.4 SP2 (Feb 01, 2012)

Wed, 01 Feb 2012 15:23:24 GMT

Notes
This SP2 release add an important feature to the CSV Log Provider. It's now possibile to store a personalized label into each log, in order to make it easy to identify or group log.
Let's say, for example, that you have 10 packages in your ETL solution, and each time you have to load your data, you need to execute all those 10 packages. In order orders, you have a batch made of 10 packages. It would be nice if all logs - one for each package - can be identfied as a whole and grouped togheter, in order to quickly identify all the log of a articular batch. The new "ExecutionLabel" attribute will help to achieve this.

A useful ExecutionLabel can be obtained using SQL Server Agents Token. For example:
LABEL=$(ESCAPE_SQUOTE(JOBID))_$(ESCAPE_SQUOTE(STRTDT))_$(ESCAPE_SQUOTE(STRTTM))

ChangeLog

Updated the CSV Log Provider in order to write the status of the log file in the header.
- An OPEN status means that the log file is being written.
- A CLOSED status means that the log files has been written correctly.
- A file can be loaded into the database log only if is in the CLOSED state.
CSV Log files have 2 additional rows in the header: one for the FileStatus and one for the ExecutionLabel values.
- File format has been update to 4 from 3. (Only the header section of the file has been changed).
CSV Log Provider will now display EndTime value to the Console
Updated the import-log-data.sql to correctly load file with format 3 (the old one) and 4 (the new one).
Updated database schema to version 19 in order to store the new ExecutionLabel value

Updated Release: 1.1.2008.4 SP2 (Feb 01, 2012)

manowar — Wed, 01 Feb 2012 14:41:41 GMT

Notes
This SP2 release add an important feature to the CSV Log Provider. It's now possibile to store a personalized label into each log, in order to make it easy to identify or group log.
Let's say, for example, that you have 10 packages in your ETL solution, and each time you have to load your data, you need to execute all those 10 packages. In order orders, you have a batch made of 10 packages. It would be nice if all logs - one for each package - can be identfied as a whole and grouped togheter, in order to quickly identify all the log of a articular batch. The new "ExecutionLabel" attribute will help to achieve this.

A useful ExecutionLabel can be obtained using SQL Server Agents Token. For example:
LABEL=$(ESCAPE_SQUOTE(JOBID))_$(ESCAPE_SQUOTE(STRTDT))

ChangeLog

Updated the CSV Log Provider in order to write the status of the log file in the header.
- An OPEN status means that the log file is being written.
- A CLOSED status means that the log files has been written correctly.
- A file can be loaded into the database log only if is in the CLOSED state.
CSV Log files have 2 additional rows in the header: one for the FileStatus and one for the ExecutionLabel values.
- File format has been update to 4 from 3. (Only the header section of the file has been changed).
CSV Log Provider will now display EndTime value to the Console
Updated the import-log-data.sql to correctly load file with format 3 (the old one) and 4 (the new one).
Updated database schema to version 19 in order to store the new ExecutionLabel value

Released: 1.1.2008.4 SP2 (Feb 01, 2012)

Wed, 01 Feb 2012 14:41:41 GMT

Notes
This SP2 release add an important feature to the CSV Log Provider. It's now possibile to store a personalized label into each log, in order to make it easy to identify or group log.
Let's say, for example, that you have 10 packages in your ETL solution, and each time you have to load your data, you need to execute all those 10 packages. In order orders, you have a batch made of 10 packages. It would be nice if all logs - one for each package - can be identfied as a whole and grouped togheter, in order to quickly identify all the log of a articular batch. The new "ExecutionLabel" attribute will help to achieve this.

A useful ExecutionLabel can be obtained using SQL Server Agents Token. For example:
LABEL=$(ESCAPE_SQUOTE(JOBID))_$(ESCAPE_SQUOTE(STRTDT))

ChangeLog

Updated the CSV Log Provider in order to write the status of the log file in the header.
- An OPEN status means that the log file is being written.
- A CLOSED status means that the log files has been written correctly.
- A file can be loaded into the database log only if is in the CLOSED state.
CSV Log files have 2 additional rows in the header: one for the FileStatus and one for the ExecutionLabel values.
- File format has been update to 4 from 3. (Only the header section of the file has been changed).
CSV Log Provider will now display EndTime value to the Console
Updated the import-log-data.sql to correctly load file with format 3 (the old one) and 4 (the new one).
Updated database schema to version 19 in order to store the new ExecutionLabel value

Updated Release: 1.1.2008.4 SP2 (Feb 01, 2012)

manowar — Wed, 01 Feb 2012 14:31:44 GMT

ChangeLog

Updated the CSV Log Provider in order to write the status of the log file in the header.
- An OPEN status means that the log file is being written.
- A CLOSED status means that the log files has been written correctly.
- A file can be loaded into the database log only if is in the CLOSED state.
CSV Log files have 2 additional rows in the header: one for the FileStatus and one for the ExecutionLabel values.
- File format has been update to 4 from 3. (Only the header section of the file has been changed).
CSV Log Provider will now display EndTime value to the Console
Updated the import-log-data.sql to correctly load file with format 3 (the old one) and 4 (the new one).
Updated database schema to version 19 in order to store the new ExecutionLabel value

Updated Release: 1.1.2008.4 SP2 (Feb 01, 2012)

manowar — Wed, 01 Feb 2012 14:24:58 GMT

ChangeLog

Updated the CSV Log Provider in order to write the status of the log file in the header.
- An OPEN status means that the log file is being written.
- A CLOSED status means that the log files has been written correctly.
- A file can be loaded into the database log only if is in the CLOSED state.
CSV Log files have 2 additional rows in the header: one for the FileStatus and one for the ExecutionLabel values.
- File format has been update to 4 from 3. (Only the header section of the file has been changed).
CSV Log Provider will now display EndTime value to the Console
Updated the import-log-data.sql to correctly load file with format 3 (the old one) and 4 (the new one).
Updated database schema to version 19 in order to store the new ExecutionLabel value

Created Release: 1.1.2008.4 SP2 (Feb 01, 2012)

manowar — Wed, 01 Feb 2012 14:22:24 GMT

ChangeLog
-Updated the CSV Log Provider in order to write the status of the log file in the header.
An OPEN status means that the log file is being written.
A CLOSED status means that the log files has been written correctly.
A file can be loaded into the database log only if is in the CLOSED state.
-CSV Log files have 2 additional rows in the header: one for the FileStatus and one for the ExecutionLabel values.
File format has been update to 4 from 3. (Only the header section of the file has been changed).
-CSV Log Provider will now display EndTime value to the Console
-Updated the import-log-data.sql to correctly load file with format 3 (the old one) and 4 (the new one).
-Updated database schema to version 19 in order to store the new ExecutionLabel value

Updated Release: 1.1.2008.4 SP1 (Jul 25, 2011)

manowar — Mon, 25 Jul 2011 13:17:18 GMT

Note
This first Service Pack is a collection of all the changes done in to changesets 86188, 86299, 87778, 88124, 91054, packaged in a single file for your convenience. You can download DTLoggedExec with the SP1 already applied or the stand-alone SP1 package and apply it yourself to your DTLoggedExec version.
The version number has not been changed because nor the executable or the plugins has been updated, but just .bat and .sql files.

ChangeLog
-Used a new strategy for version numbers. Now it will follow the following pattern Major.Minor.TargetSQLServerVersion.Revision
-Added support for Auto Configurations
-Fixed a bug that reported incorrect number of errors and warnings to Log Providers
-Fixed a buf that prevented correct casting of values when using /Set and /Param options
-Errors and Warnings are now counted more precisely.
-Updated database and log import scripts to categorize logs by projects and sections. E.g.: Project: MyBIProject; Sections: Staging, Datawarehouse
-Removed unused report stored procedures from database
-Updated Samples: 12 samples are now available to show ALL DTLoggedExec features
-From this version only SSIS 2008 will be supported

Released: 1.1.2008.4 SP1 (Jul 25, 2011)

Mon, 25 Jul 2011 13:17:18 GMT

Updated Release: 1.1.2008.4 (Mar 15, 2011)

manowar — Tue, 15 Mar 2011 10:22:54 GMT

-Used a new strategy for version numbers. Now it will follow the following pattern Major.Minor.TargetSQLServerVersion.Revision
-Added support for Auto Configurations
-Fixed a bug that reported incorrect number of errors and warnings to Log Providers
-Fixed a buf that prevented correct casting of values when using /Set and /Param options
-Errors and Warnings are now counted more precisely.
-Updated database and log import scripts to categorize logs by projects and sections. E.g.: Project: MyBIProject; Sections: Staging, Datawarehouse
-Removed unused report stored procedures from database
-Updated Samples: 12 samples are now available to show ALL DTLoggedExec features
-From this version only SSIS 2008 will be supported

Released: 1.1.2008.4 (Mar 15, 2011)

Tue, 15 Mar 2011 10:22:54 GMT

Updated Release: 1.1.2008.4 (Mar 15, 2011)

manowar — Tue, 15 Mar 2011 10:22:25 GMT

Updated Release: 1.1.2008.4 (Mar 15, 2011)

manowar — Tue, 15 Mar 2011 10:18:32 GMT

Released: 1.1.2008.4 (Mar 15, 2011)

Tue, 15 Mar 2011 10:18:32 GMT

Updated Release: 1.0.0.2 (Jun 11, 2010)

manowar — Sun, 13 Jun 2010 08:46:06 GMT

-Fixed a bug that prevented loading packages from SSIS Package Store
-Added support for {filename} placeholder in both Data Flow Profiling and CSV Log Provider

Note:
Samples and Demo Reports are available in the 1.0.0.1 release since no changes has been made to them:
http://dtloggedexec.codeplex.com/releases/view/44689

Released: 1.0.0.2 (Jun 11, 2010)

Sun, 13 Jun 2010 08:46:06 GMT