History

March 1, 2006 - v1.5.0.2

1. Support for Microsoft SQL Server 2005.
2. Revamped GUI.
3. A per-project setting is available now to take trailing spaces in character fields into account when detecting field value changes.
4. Logging options for a project can be stored now without the need to reconnect.
5. Position and width of BLOB viewer window gets restored.
6. Filter settings are persistent now.

1. Bug fixed: Fixed another problem with databases created with a case-sensitive collation. Delete log data works fine now. (#31)
2. Bug fixed: Enabling automatic record count without being connected does not throw an error anymore.
3. Bug fixed: Detecting changes in character fields with trailing spaces has been fixed. See enhancement 3)

September 12, 2005 - version 1.1.0.6

• Fixed a problem with databases created with a case-sensitive collation.

April 19, 2005 - version 1.1.0.5

• Scripting facility implemented. The MSSQLLM Scripting Engine can be used to automate repetitive tasks in a script based way. A detailed script language reference is available in the Online-Help.
• Logging options can be defined per project in the Connect to Database dialog now. The logging options in the Options dialog serve as default values when creating a new project.
• A new index for the FOREIGN KEY constraint on the column log table will be now created during the preparation.
• Transaction token logging by using the stored procedure "sp_getbindtoken" added. To use that feature, the database must be prepared with v1.1 (or higher) and the "Log Transaction Token" option in the Prepare-Wizard must be selected.
• In the Prepare-Wizard: Stored procedures got two new options "With Encryption" and "Not For Replication".
• New command line switches -i and -nosplash have been added. Use -i <filename> to specify the configuration file MSSQL LogManager should use. If -i is omitted, then 'mssqllogmanager.cfg' is used. Use -nosplash to omit the splash screen at program start.
• For browsing log data a client-side cursor is used now.

• Bug fixed: Preparing a database with a user different to 'dbo' resulted in that the database wasn't recognized as prepared when connecting the next time.
• Bug fixed: Some other minor owner/schema related problems fixed.
• Bug fixed: Problems with logging [SMALL]MONEY fields have been fixed.
• Bug fixed: Open table records through logged records works now.

June 1, 2004 - v1.0.3.1: Final v1 Release

• Some minor performance related tweaks.
• Online-Help updated.

• None

March 10, 2004 - v1.0.2.1: Public BETA 2

• Table owner and table name in the operatin log table are stored separately now. That logging metadata changes requires an unprepare of your database. You'd best exporting your logging schema with File/Export Logging Definition... Unprepare/Prepare your database, and finally import the previously exported logging schema with File/Import Logging Definition... You will loose already logged data though.
• New filter criteria "Owner" has been added.
• Multi-Select in data grids via check box.
• "Select All" and "Unselect All" in data grid's context menu has been added.
• Hitting the space bar in the log data grid will toggle the "selected" state.
• LOB columns in column log grid of type text and image are invisible per default, because they aren't used right now.
• Columns of type "timestamp" and "sql_variant" aren't shown in the treeview and will not be logged.
• COMPUTED BY columns aren't shown in the treeview and will not be logged anymore.
• Using IF (UPDATE(...)) in INSERT/UPDATE triggers.
• Improved code generation for UPDATE trigger including NOT NULL columns. Unnecessary conditions in the IF clause, for detecting changes in a column, has been removed.
• An "Use BIGINT for primary/foreign key columns" option has been added in the Prepare-Wizard, which enables you to use the data type BIGINT for primary/foreign key columns in the logging metadata (tables and stored procedures).
• Analyzing the database with displayed object descriptions is much faster now.
• PKEYx_VALUE (x=1..5) columns in MSSQLLM$OPERATION are of type NVARCHAR now.
• Some more changes in the logging data model. Removed the IMAGE and TEXT column in MSSQLLM$COLUMNLOG. Using NVARCHAR/NTEXT in general.
• Installed ADO-Version is shown in the About-Dialog now.
• Column USER_NAME in operation log table is a NVARCHAR(128) now.
• Using fixed constraint names, of style DF_<TABLE>_<COLUMN>, for DEFAULT definitions in the operation log table.
• Using the UDT SYSNAME (aka NVARCHAR(128)) in logging metadata for columns, storing database object names.
• New option "Single DELETE statement with current filter criteria" added in the Options-Dialog. This enables one to specify whether "Delete all records" will execute a simple DELETE FROM ... statement with the current filter criteria (option = checked) or deleting all records by iterating through the result set (option = unchecked).
• New option "Try to create the logging trigger on LAST position" in the Options-Dialog added. Select this option, if you want the logging trigger to be created at the last position, but only, if there isn't already another LAST trigger.
• A new logic has been added, to handle columns bigger than "Max. column value length" in the Prepare-Wizard. Such a column will be logged in a LOB column OLD_VALUE_TEXT resp. NEW_VALUE_TEXT.
• New Online-Help.

• Bug fixed: UPDATE Trigger uses now an INNER JOIN instead of FULL OUTER JOIN for joining the DELETED and INSERTED temp tables. As a general rule, you should never update primary key column values, otherwise you might get an unexpected result.
• Bug fixed: DATETIME column in operation log table was renamed to DATE_TIME to avoid name clashes with the DATETIME data type. Be aware, the auto load setting facility of the log data grid doesn't consider that name change, so initially, you won't see any data for that column, as it will point to the previously used DATETIME column name. Go into the registry and delete the following registry key completely:
  HKEY_CURRENT_USER\Software\MSSQLLogManager\Databases
  What a hack, I know. I'm sorry.
• Bug fixed: Occasional exception, when deleting log data, should be fixed now.
• Bug fixed: Using the date/time filter criteria should be more stable now. In general, the date/time format 'yyyymmdd hh:nn:ss' is used internally now, to build the SQL expression for the filter criteria.
• Bug fixed: If there is an existing trigger at the last position, then the creation of the logging trigger doesn't fail anymore. The log trigger will be created at last position, if the "Try to create the logging trigger on LAST position" option (see Options-Dialog) is checked, and if there isn't already a LAST trigger.
• Bug fixed: Fixed an owner related bug, showing wrong column names for equally named tables having a different owner.
• Some minor bug fixes

February 9, 2004 - v1.0.0.0: Public BETA 1

• Core functionality and GUI ported from IB/ADS LogManager to MSSQL LogManager supporting Microsoft SQL Server 2000.