I’ve released couple of hours ago the SP2 of my DTLoggedExec tool.
For those who don’t know it, it’s a DTEXEC replacement, useful to execute SSIS and having logging provided right from the engine and not from the package itself.
More info can be found here:
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:
- 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
As usual the download is available for free here: