What's new in DTLoggedExec 1.1.2008.4 SP2
Aug 29, 2012
- 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
New in DTLoggedExec 1.1.2008.4 SP1 (Jul 28, 2011)
- 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
New in DTLoggedExec 0.2.2.0 Beta (Sep 30, 2009)
- Added logging of expression used by variables for which the "EvaluateAsExpression" property is true.
- Fixed the bug the prevented to log properly Custom Events (CodePlex id# 20513)
- Fixed a bug that prevented to log properly all the container properties in case of error
- Added support for "Params" commandline options
- Released CSV log provider
- Handled exceptions when loaded configuration tries to configure non-existing objects
- Changed the ILogProvider interface to allow Log Provider to get the ExecutionGUID value from the main program
- Changed the Console and Null log providers to support the new ILogProvider interface
- Changed the header of the *.dtsDataFlowProfile in order to store package, version and execution GUIDs
- Changed .sql files to import Profiled DataFlow data in SQL Server
- Updated DTLoggedExecDB database
- Released scripts to load CSV data proceduced by CSV Log Provider into SQL Server
New in DTLoggedExec 0.2.1.4 Beta (Jan 15, 2009)
- Modified the console log provider so that before the package starts all connection manager list their connection string
- Added DataFlow profiling support through "DataFlowProfile" switches.
- Changed the ILogProvider interface to support configuration of log providers
- Changed the Console and Null log providers to support the new ILogProvider interface
- Added a database script to create the DTLoggedExecDB where you can store the DataFlow profiled data, using supplied scripts