Softpedia >Windows >Internet >Servers >Database Utils >ApexSQL Log >  Changelog

ApexSQL Log Changelog

What's new in ApexSQL Log 2019.02.1245

Jun 11, 2023
  • Fixes:
  • Cannot resolve the collation conflict in the UNION operation.
  • Operation data is not shown for tables with page compression.

New in ApexSQL Log 2019.02.1254 Patch (Dec 8, 2020)

  • Fixes:
  • Cannot resolve the collation conflict in the UNION operation
  • Operation data is not shown for tables with page compression

New in ApexSQL Log 2019.02.1251 Patch (Aug 28, 2020)

  • Fixes:
  • Connection to a remote SQL Server instance results in a timeout when auditing the remote instance

New in ApexSQL Log 2019.02.1249 Patch (Jul 10, 2020)

  • Fixes:
  • Operation data is not shown for compressed nvarchar columns with less than 2 characters

New in ApexSQL Log 2019.02.1247 Patch (Mar 20, 2020)

  • Fixes:
  • The 'unknown schema' is displayed when alter/drop view operation is audited in case there are un-assigned index in the table view

New in ApexSQL Log 2019.02.1245 (Jan 30, 2020)

  • Fixes:
  • Cannot resolve the collation conflict in the UNION operation
  • Operation data is not shown for tables with page compression

New in ApexSQL Log 2019.01.1240 (Dec 18, 2019)

  • Enhancements:
  • SQL Server 2019 support
  • Fixes:
  • Arithmetic overflow error for data type smallint, value = 32768 error occurs when auditing a database with over 32768 users
  • "Operation Create Table is missing UNDO/REDO script" error is encountered in undo/redo script for create/alter table operations
  • CLI command created in the end of export wizard is missing /v (verbose) and /f (force) switches
  • Rebuild index operation redo drops the entire table

New in ApexSQL Log 2018.05.1233 (Jun 21, 2019)

  • Software Transaction Agreement is added as a new step in the installation wizard and updated in accordance with https://www.quest.com/legal/sta.aspx

New in ApexSQL Log 2018.05.1228 (May 23, 2019)

  • Fixes:
  • Rebuild index operation is now properly replayed in redo scripts
  • Redo script of rebuild index operations drops the entire table
  • "Object reference not set to an instance of an object" error is encountered when auditing DDL operations over whole log on SQL Server2014 and older
  • "Operation Create/Alter Table is missing UNDO/REDO script" error is encountered in undo/redo scripts for create/alter table operations in SQL Server 2014 and older

New in ApexSQL Log 2018.04.1223 Patch (Feb 7, 2019)

  • Redo script of rebuild index operations drops the entire table
  • "Object reference not set to an instance of an object" error is encountered when auditing DDL operations over whole log on SQL Server2014 and older
  • "Operation Create/Alter Table is missing UNDO/REDO script" error is encountered in undo/redo scripts for create/alter table operations in SQL Server 2014 and older

New in ApexSQL Log 2018.04.1222 Patch (Feb 1, 2019)

  • Fixes:
  • Redo script of rebuild index operations drops the entire table
  • "Object reference not set to an instance of an object" error is encountered when auditing DDL operations over whole log on SQL Server2014 and older
  • "Operation Create/Alter Table is missing UNDO/REDO script" error is encountered in undo/redo scripts for create/alter table operations in SQL Server 2014 and older

New in ApexSQL Log 2018.04.1219 (Dec 25, 2018)

  • Fixes:
  • Aborted transactions are not audited
  • "Trial period has expired. Purchase the software to continue using it or contact [email protected]" message is displayed when ApexSQL Log batch script is run after the trial period has been extended
  • Field value grid filter does not affect audited result when applied
  • All conditions aside from the first one in the list are not applied in the field values filter if multiple conditions are defined
  • Application doesn't automatically connect to the audited database when undo/redo script is connected
  • The Find next option does not cycle through the results
  • “Failed to load project” error is encountered when application is restarted with “start as admin”
  • Default value for the custom filter is not set to current day
  • The Ctrl+A shortcut does not work on results audited to grid
  • Syntax highlighting does not affect batch scripts
  • It is not possible to select last row when undo/redo script is opened via integrated editor
  • The sa login is locked out when wrong password is provided for the sa account
  • “Failed to load project” error is encountered when starting application with insufficient privileges
  • Find panel is not initiated via ctrl+F shortcut
  • The same SQL Server instance can be added multiple times in the activation panel
  • Enhancements:
  • Created scripts can now be saved as PowerShell
  • The Primary Key column value is now included in the operation details pane for each operation
  • The application now automatically checks validity of the selected data sources
  • 24h format can now be used in the custom filter when Windows regional format settings imply 24-hour format
  • Paging is added to the HTML exports
  • Column order can now be changed in grid using drag-and-drop
  • Information message added that TDE encrypted database cannot be audited if the afore mentioned database is selected for auditing
  • Information message added that SQL Server instances hosted on Linux OS cannot be audited
  • Changes:
  • The application now requires Microsoft .NET Framework 4.7.2

New in ApexSQL Log 2018.03.1213 (Nov 8, 2018)

  • Fixes:
  • "Error opening connection: Invalid connection string attribute" error is encountered when Windows Authentication is used to connect to a database in a specific case
  • SQL login used to connect to a database gets locked out on servers which have account locking set up for failed login attempts in case when correct password is provided
  • Changes:
  • CLI functionality is now available during the trial period

New in ApexSQL Log 2018.02.1211 (Oct 18, 2018)

  • Enhancements:
  • SQL Server 2019 CTP 2.0 support
  • New error handling and send logs functionality
  • Improved application installer with a dark theme
  • New application icon
  • The ‘Make new folder’ button has been added to all browse for folder dialogs
  • Fixes:
  • Date/time filter is not presented in the regional format if Spanish language and regional settings are used

New in ApexSQL Log 2018.01.1198 (Nov 29, 2017)

  • Enhancements:
  • SQL Server 2017 support
  • High DPI and 4K resolution support
  • Log reading is now up to 20,000% faster for all databases that contain over 1,000 SQL tables
  • Fixes:
  • The "Activation limit exceeded" warning is encountered when user tries to activate the node in active-passive cluster environment with a single license after the failover occurs
  • Data sources used in the undo/redo wizard are not listed in the “Datasources” section in the recovery summary
  • The "Object reference not set to an instance of an object“ error is encountered when clicking the Add pattern button in the Select data sources step of the wizard in a specific case
  • The Send logs feature does not include server-side components log files
  • The Get updates dialog is not closed via Esc key
  • Date/time formats are inconsistent throughout the application
  • Vertical scroll bar doesn't work in the Browse for folder form in the installation wizard
  • Changes:
  • New light, blue and dark themes are now available

New in ApexSQL Log 2018.01.1197 (Nov 28, 2017)

  • Enhancements:
  • SQL Server 2017 support
  • High DPI and 4K resolution support
  • Log reading is now up to 20,000% faster for all databases that contain over 1,000 SQL tables
  • Fixes:
  • Filter dialog is not correctly scaled on 125% size Windows zoom setting
  • Query processing lasts more than 20 minutes for databases that contain more than 1000 tables
  • The message "Activation limit exceeded" is encountered when user tries to activate the node in active-passive cluster environment with a single license after the failover occurs
  • Data sources used in the undo/redo wizard are not listed in the “Datasources” section in the recovery summary
  • The „Object reference not set to an instance of an object“ error is encountered when clicking the Add pattern button in the “Select data sources” step of the wizard in a specific case
  • The Send logs feature does not include server-side components log files
  • The "Get updates" dialog is not closed via Esc key
  • Date/time formats are inconsistent through application
  • Vertical scroll bar doesn't work in the Browse for folder form in the installation wizard
  • Changes:
  • Users can now choose between light, blue or dark themes

New in ApexSQL Log 2017.01.1185 Patch (Nov 15, 2017)

  • Enhancements:
  • Log reading is now up to 20,000% faster for all databases that contain over 1,000 SQL tables

New in ApexSQL Log 2017.01.1180 (May 24, 2017)

  • Enhancements:
  • Support for SQL Server 2017 CTP 2
  • Fixes:
  • Double click on a blank space near the grid filter text in the transactions grid opens Customization menu
  • No results are displayed when Field values filter is applied in the main grid
  • The “Token StarAttribute in state Error would result in an invalid XML document.” error is encountered when transactions with certain characters from Chinese alphabet are exported
  • Object of type 'System.DBNull' cannot be converted to type 'System.DateTime'" error is encountered when data is copied from the first to the second text box in the Period grid filter in the main grid
  • The "Some fields and/or values are not set." warning message is encountered when the value of Comparison column is set to IsNull and Value column is left empty in the Field values filter for the specified table
  • The application dialogs are overlapping on a 4K screen resolution
  • Identifying transaction log files and reading of transaction logs during auditing task suffers a 20 seconds stall on Windows 10 Creators update
  • Changes:
  • Before-after reports now shows all table columns regardless if they were affected by the change or not

New in ApexSQL Log 2016.03.1166 (Sep 5, 2016)

  • Fixes:
  • Detection of online transaction log and auditing processes are slower up to 1000% on Windows 10 with the anniversary update
  • The 'old table ID mapping' information is now saved within session

New in ApexSQL Log 2016.02.1162 (Jun 3, 2016)

  • Enhancements:
  • SQL Server 2016 support
  • Users can now choose between 3 themes: white, colorful or dark
  • The 'Find operation' process performance improved up to 500%
  • Added "exclude_tables" CLI switch
  • Fixes:
  • The Windows taskbar is not shown on hover, when the Auto-hide the taskbar option is checked, and the application is maximized
  • The 'missing connection to database' error is encountered if check syntax process is canceled
  • The 'beginning' and 'end' of data in Grid are inverted
  • The 'open script' action is not offered when exporting to Bulk from Grid
  • Export or create before-after report to database are not available in the context menu
  • Server-side components are incorrectly installed on cluster nodes when installation is performed remotely
  • The 'The communication object, System.ServiceModel.ServiceHost, cannot be used for communication because it is in the Faulted state' error is encountered in rare cases
  • Application doesn't show proper dialogs in very high resolution settings
  • Cannot detect SQL Server process on Windows server 2008 when server process ID > 65535
  • Batch script editing is lost when 'Save batch script' button is clicked in the export wizard
  • Deprecated switch /ssa is still shown in CLI help
  • The 'A generic error occurred in GDI+.' error is encountered when auditing specific blobs
  • There is no limit to size of shown data in the Operation details pane
  • The 'Object reference not set to an instance of an object.' error is encountered if incorrect SPID is provided
  • Buttons are crowded in the Export results dialog
  • The 'Aborted' checkbox is not reset to default setting when Default button is clicked
  • Clear button does not reset Duration minimum value in grid filter
  • Inappropriate recovery model information is displaye din case when incorrect password is specified
  • The "Object reference not set to an instance of an object" error is encountered when application is minimized if grid results are empty
  • The standard windows keyboard shortcuts "Win key “+” arrow key" doesn't work

New in ApexSQL Log 2016.01.1149 (Nov 24, 2015)

  • Enhancements:
  • Server side components no longer include any extended stored procedures
  • Before-After report generation
  • Export directly to database
  • Continuous auditing - allows the user to carry on with auditing at the exact point where the previous auditing session was finished
  • SQL Server 2016 CTP3 support
  • Added "exclude_users" CLI switch
  • Added support for backup filename patterns in datasource selection (also supported through CLI)
  • No more limit on script size when editing and executing created scripts
  • Fixes:
  • The "RECORD CHANGE HISTORY COULD NOT BE RECONSTRUCTED FOR UPDATE ON table" when reading internal cluster key with UNIQUIFIER column
  • The "Object reference not set to an instance of an object" error is thrown during bulk export process
  • The /table switch doesn't support schema filter
  • Application doesn't filter transaction log properly if UAC is on
  • The "There is not enough space on the disk" issue is encountered when large number of transaction log files is used
  • Running CLI command cannot be stopped with CRTL+C if the process hangs
  • Application CLI hangs when auditing and creating a bulk script export for specific set of transaction log backups
  • The 'A generic error occurred in GDI+' error is encountered in a specific case when auditing a table that has entire SQL diagrams stored in the sysdiagrams table
  • Application doesn't report if compatibility mode is not appropriate
  • Auditing process crashes in specific cases when cache file exceeds 2GB
  • All results for dropped tables are removed from the grid if grid DDL filter is used
  • The "Binary stream '0' does not contain a valid BinaryHeader. Possible causes are invalid stream or object version change between serialization and deserialization" error is encountered when connecting remotely to SQL Server 2005 x86 from x64 machine
  • The '/to:arg' filter cannot be used without '/from:arg' switch
  • The 'last 24h' and 'whole transaction log' CLI switches do not exist
  • Changes:
  • Application now requires .NET framework 4.5.2

New in ApexSQL Log 2014.04.1133 (Dec 27, 2014)

  • Fixes:
  • The "Operation is missing UNDO/REDO script" error is encountered when creating UNDO or REDO script for DDL operations
  • The application does not show transaction for tables with page compression when database is in compatibility mode
  • The "System.Data.SqlTypes.SqlNullValueException" is thrown when transaction log contains incomplete data
  • The 'ApexSQL Log has stopped working' error is encountered when opening previously saved session while exporting process is running
  • Missing warning message that table ID is already mapped if multiple table mapping is initiated
  • Missing confirmation prompt when filter clear is initiated in GUI
  • The 'Group by' filters in the grid do not work
  • The "System.IO.FileNotFoundException" error is encountered when trying to open Options on a specific Windows Server 2003
  • The Schema operations filter is missing filter by Schema
  • The 'Collection was modified; enumeration operation may not execute' error is encountered if a session is active during the application update
  • Deleted users are not shown if existing users are filtered out via the grid filter

New in ApexSQL Log 2014.03.1129 (Dec 3, 2014)

  • Fixes:
  • The "Error opening connection: Invalid connection string attribute" error is encountered when trying to connect to database when either server, username or password contains special characters ("';)
  • The application hangs during the creation of a REDO script when performing a conversion of datetime
  • The "Operation 'Drop object' is missing UNDO/REDO script" error is encountered when creating UNDO or REDO script for dropped DDL operations
  • The auditing process stops during "Initialize engine" step when auditing SQL 2005 database on Windows Server 2008
  • The exporting process cannot be completed when exporting transaction log file backups without on-line transaction log to XML from CLI
  • The "External component has thrown an exception" error is encountered when trial period is extended on remote SQL Server

New in ApexSQL Log 2014.02.1121 (Dec 3, 2014)

  • Fixes:
  • The "Object reference not set to an instance of an object" error is encountered when using the "Old table ID mapping" option when transactions contain incomplete information
  • The application cannot complete auditing and the GUI hangs when auditing damaged transaction logs
  • The application cannot read compressed SQL Server 2014 backups
  • The batch script generated via the "Create batch file" option contains an incorrect value for the "/from" switch for the last 24 hours time range
  • The "System.ArgumentNullException - Value cannot be null" error is encountered when copying from the Undo or Redo script pane when no code is selected
  • The "Object reference not set to an instance of an object" error is encountered when exporting results into an HTML file via the CLI
  • The "At least one table must be selected when the DDL filter is not used" message is shown when no tables exist in the transaction log files added to the session, and navigation through Filter setup is blocked

New in ApexSQL Log 2014.01.1116 (Dec 3, 2014)

  • Enhancements:
  • The application now fully supports SQL Server 2014
  • Automatic recognition of the database recovery model
  • An option to purge old application log files is added
  • Precision up to milliseconds is added to the Time range filters
  • Added the new "The session wizard auto loads SQL logs to analyze" option in the General section of the Options dialog
  • Fixes:
  • The script created via the "Export to SQL BULK" cannot be executed
  • The "System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values" error is encountered when trying to connect to a database using the login mapped to a database user with the db_owner role
  • The "Object reference not set to an instance of an object." error is encountered if an incorrect path is selected in the Export undo script option
  • The "Column name or number of supplied values does not match table definition" error is encountered when running a script created via the Export to SQL file option
  • The "External error has thrown an exception" error is encountered when trying to manually activate a remote SQL Server instance
  • The "Adding a server failed" error is encountered when trying to activate a SQL Server instance with the same name as an instance already activated, but on a different machine
  • The Time range filter shows incorrect result set when the main grid is refreshed
  • The Users filter is not correctly filtering transactions in the main grid
  • When Select All Operations in Transactions is selected in the main grid, all operations in the selected transaction(s) are not shown in a specific case
  • The "Object reference not set to an instance of an object. Type: System.NullReferenceException" is encountered when creating the Undo or Redo script for the specific case
  • The application crashes when reading online transaction log files and server side auditing is used in a specific case
  • The Copy Rows to the Clipboard option does not copy the rows to the clipboard
  • The "The system cannot find the file specified" errors is logged in the application log files when trying to read specific transaction log backup files
  • The DDL filters are filtering the result set incorrectly after loading an application object filter .axof file
  • The Other option in the application Options | Script editor| Output Format and Editor cannot be configured
  • The "The constructor to deserialize an object of type 'ApexSql.Log.LogOperationData' was not found." error is encountered when clicking rows in the main grid in a specific case
  • Values for binary columns are not shown as binary when scripting user defined types that inherit the varbinary type
  • The Server selection in the Connect to server dialog in the Activation form is not locked in the activation dialog
  • When a backup is removed from the file list in the Select SQL logs to analyze step, transaction log details are removed from all backups in the file list
  • Some dialogs cannot be closed via the Escape key
  • The "The path is not of a legal form" error is encountered when incorrect path is provided in the Output path for Export/Create batch file
  • The Activation status is shown as Unknown when the trial expires on a server with no server side components
  • The application cannot access the online transaction log and the "The system cannot find the file specified" message is logged in the application log files in a specific case
  • The "Object reference not set to an instance of an object" error is encountered when creating the undo/redo script in a specific case
  • The session wizard cannot complete the auto loading of SQL logs process in a specific case
  • The "Export to SQL BULK" option generates a SQL script that cannot be executed in a specific case
  • The "Object reference not set to an instance of an object" error is encountered when using the "Open results in grid view" option in a specific case
  • The "There was an error reflecting type 'ApexSql.Log.Gui.Classes.Data.LogProjectFilter' Error" error is encountered when using the "Save filter" option in a specific case
  • The "Unknown error has occur" message is shown when trying to use the "Manage server-side components on local servers" option in a specific case
  • There's no option to check/uncheck all Users in the main grid filter
  • Updated columns are not highlighted in the Operations details tab
  • Changes:
  • New user interface that follows Metro UI style
  • The "Create undo script" and "Create redo script" options in the main menu now create scripts only for the selected transactions
  • Windows XP is no longer supported
  • Known limitations:
  • The "ApexSqlServerHelper failed with -1073741819" error is encountered when reconstructing updates on a clustered table

New in ApexSQL Log 2013.01.1098 (Dec 3, 2014)

  • Enhancements:
  • Faster and easier server-side components (SSC) installation for remote servers
  • Optimized session wizard with simplified data sources selection (unified backup, tlog and detached file adding interface)
  • Performance improvements - up to 12 times faster auditing via GUI, and up to 5 times faster result grid filtering on large transaction logs (with over one million operations)
  • The application now fully supports Windows 8.1 and Windows Server 2012 R2
  • Fixes:
  • If schema related operations are filtered using the "Filter" feature, and only transaction log backups are used as the source, an incomplete set of data and schema related operations is shown in the main grid
  • The "Date/Time range" filter shows wrong results
  • The application crashes when sorting results in the main grid by transaction ID
  • Filtering results using the "User tables" option doesn't work properly for the specific database
  • The application prompts to install server-side components (SSC) when sending logs, even if a proper SSC version is already installed
  • The Find feature doesn't work properly if search is started from the beginning of the main grid while searching upwards
  • The text about the trial version limitation is cut off in the about dialog
  • The "Object reference not set to an instance of an object." error is encountered if the "Find next" command is used after the "Check" option while the application still read logs
  • The "Files cannot be replaced" error is encountered while installing server-side components on SQL Server 2005
  • A transaction log backup cannot be found on a remote SQL Server 2000 when the "Server usage" option is On
  • An incorrect error message is shown in the GUI if the transaction log file is inaccessible
  • Both ApexSQLLog2008 and ApexSQLLog2011 folders are created in AppData when using the application
  • The "Server activation center" doesn't change application status to Activated upon successful manual activation
  • Improper grammatical structure in the "Server activation center" Details if the selected server is unavailable or has invalid credentials
  • The "Activate" button in the "Server activation center" is unpredictably enabled or disabled when two or more servers without SSC installed are enlisted
  • The application crashes when applying the "Date/time" filter option changes
  • Navigating the resulting grid using Ctrl+Home and Ctrl+End key combination doesn't work properly
  • The "Delete Filter" command unsorts the resulting grid sorted previously
  • After refreshing the resulting grid, previously deselected columns in the "Select columns" dialog are selected and re-shown in the resulting grid
  • The resulting grid empties and cannot be repopulated after the DDL filter is applied on a database that contains only DDL changes
  • SQL Server activation state is lost in case an activated latest patched installation is uninstalled and replaced with the public application version
  • When using the custom "Day/time" filter, the committed DDL and DML changes aren't displayed
  • When filtering DML operations, selecting "Update" and "Delete", without "Insert", displays updated objects only
  • The application is unable to access transaction log backups created on network drive mapped via XP_CMDSHELL system procedure
  • The application stops responding for a short time when connecting to SQL Server to retrieve server side logs using the "Send logs" option
  • "The [DBNETLIB][ConnectionWrite (send()).]General network error." error is encountered when "Opening log sources" dialog is closed due to insufficient permissions to access transaction log backups
  • Canceling the "Check all" feature of the "Find" dialog starts the searching process that cannot be canceled
  • The application crashes if the "Find" dialog's "Check all" with the "Details" option is performed on a specific database with transaction log backup included as an additional source
  • Incomplete data is exported after the "Export to HTML" feature is used twice to export the same resulting grid
  • The application stops responding when trying to open a specific test database
  • Incorrect text spacing in the "Filter defaults"-"Other" dialog
  • The "An error occurred while reading the backup file: CreateFile() failed ..." error is encountered when opening projects with remote database backup
  • The application is unable to read data from databases re-attached to the remote SQL Server
  • Excessive logging if reconstruction of UPDATE statement fails
  • The "Check all" feature in the "Find" dialog deselects previously checked items from the resulting grid
  • "Operation ALTER TABLE at is missing UNDO script." is generated as an ALTER TABLE undo script in case both online transaction log and additional transaction log backups are used as the source
  • Missing desktop shortcut icon on Windows 8 and Windows Server 2012
  • The "Specified argument was out of the range of valid values" error is encountered when removing "Unknown server" using the "Server activation center" dialog
  • The "Update error: Update process completed successfully, but can't run PostProcessorAssembly" error is encountered when the update ends using the "Automatic Update Service" feature
  • The application stops responding while reading AdventuresWork2012 database transaction log with enabled filter for user column
  • The application stops responding while reading the transaction log backup using a particular database
  • The "Top Level Exception stack trace at System.Drawing.Graphics.CheckErrorStatus(Int32 status)" error is encountered when selecting and deselecting rows in the resulting grid
  • Wrong copyright year information displayed in the "About" dialog
  • Multiple database backups must be added manually one by one using the "Database backups" dialog
  • The ApexSql.Log.LogException" error is encountered when the database being audited is deleted, and a new project started
  • When filtering main grid results by the "Date and Time" column, sorting is changed from "Begin Time" to alphabetical order of the "Operation" column
  • The application is being deactivated randomly, and requires reactivation
  • The "Exception occurred: OpenProcess() failed (2): Access is denied." error is logged when auditing any database on SQL Server 2012 x64
  • The "System.ArgumentOutOfRangeException" error is encountered when removing all enlisted servers from the "Server activation center" dialog
  • The selected enlisted transaction log or backup file is not correctly marked when selected through the "Project" dialog
  • The resulting grid data is not refreshed if Page Down button is used and DML operations are filtered out
  • The "Failed accessing activation information." error is encountered when connecting to the server database
  • The Progress bar and Cancel button are shown on the "Database backups" tab even if no backup is selected for loading
  • Sorting recent projects in the "Project management" dialog does not work
  • The application doesn't handle the Up and Down Arrow keys properly for the resulting grid navigation
  • The Apply filter pane remains visible after deleting the filter
  • Navigating the resulting grid via Up/Down arrows or PgUp/PgDown keys doesn't work correctly if remote SQL Server database is being audited
  • Question marks instead of dots are shown in the connection failed dialog
  • Transaction log files cannot be read because of insufficient permissions on project edit even if they were successfully added
  • Project wizard column descriptions cannot be read as the horizontal scroll bar is missing
  • The "ApexSql.Log.SsaFailedException" error is encountered when auditing a particular database and the "Server usage" option is On
  • The "ApexSql.Log.LogException" error is encountered if connection to the database is lost and resulting grid refreshed while the "Server usage" option is On
  • If the checked rows are filtered out after applying a new filter, random rows will appear as checked
  • The commands attached to the Quick access toolbar are reset after the application restarts
  • Commands "Close project", "Save as...", "Print" and "Print preview" don't have tooltips when added to the Quick access toolbar
  • Number of checked rows isn't updated in the status bar after being modified via the "Check all" command using the "Find" dialog
  • Columns in the "Server activation center" can be shrunk to zero width
  • Enlisted rows in "Old table ID mapping" need to be removed twice to be deleted
  • The "Remove" option in "Transaction logs" dialogs removes the selected, not the checked files
  • A wrong error message is encountered when entering Connection monitor account details if SQL Server authentication is used and Windows user details entered
  • Statistics information is not updated if selected rows are checked using the Space key
  • Invoking help leads to non-existing pages
  • Information icons with tooltip descriptions are missing for some options
  • Inconsistent tooltip buttons in the "Project" dialog
  • The "Object reference not set to an instance of an object" error is encountered when repeating the search process for the existing text in the resulting grid, with different search options selected
  • Wrong resulting grid row selection info if data is filtered out
  • The "Collection was modified after the enumerator was instantiated." error is encountered when sorting the grid while the application is reading data sources
  • Wrong information shown about searched operations if searching is started while the application is reading data sources
  • The "Requested Clipboard operation did not succeed." error is encountered on copying the DML operations value to clipboard
  • The application stops responding if the "Find" dialog is used with lots of data in the grid and all search options are checked
  • The "Find" feature is omitting the selected record from search
  • The icon indicating the DDL filter is changed remains gray if the "Objects: not set" option is used
  • The "Applications: not set" text is unchanged even if "Show operations made by unknown applications" is changed
  • The "Hosts: not set" text is unchanged even if "Show operations made by unknown client host" is changed
  • Description items added on project wizard or filter cannot be edited
  • If all data is filtered out, the "Refresh" option in the menu is enabled and the "Refresh" option on the context menu is disabled
  • If all data is filtered out, the "Find" option in the "menu is enabled and the "Find" option on the context menu is disabled
  • If all data is filtered out, the "Copy rows to clipboard" option in the menu is enabled and the "Copy rows to clipboard" option on the context menu is disabled
  • Saved project shows no database name in the "Project management" dialog if used database is the SQL Server default one
  • Calendar months cannot be properly set using the visual calendar in the "Time range" filter feature
  • The user is not prompted to save previously changed filter settings before loading other filter settings file
  • The "Clear recent history" option is wrongly positioned in the "Options" dialog
  • Using the "Check all" button in the "Find" dialog clears the checked state from all records before setting it for the records fulfilling the search criteria
  • The "Startup action" option's tooltip on the "General" tab in the "Options" dialog contains too much text to be read while it's displayed as tooltip closes
  • The last selected row does not get checked when the "Check selected" command is selected and the selection is made by the Shift+Left mouse button click
  • The rows checked before applying a filter are shown as checked in the grid, but they all uncheck after scrolling the grid
  • Impossible to type uppercase letters in the "Find" dialog if there are lowercase words in the search history beginning with the same letters
  • The Search history list in the "Find" dialog cannot be cleared
  • The "Processing logs" progress bar shows wrong information while exporting data using the "Project" dialog
  • The application always asks to save changes in the current project when closing, or on opening a new one, even if nothing is changed
  • When adding database backups, the last used location is opened instead of the one used by SQL Server
  • Removed transaction logs are enlisted again on editing project in the "Transaction logs" section
  • Searching for backups cannot be canceled or finished if a project with the previously removed backup is being edited
  • Visual inconsistencies exist in the "Options" dialog if application is started under 120 DPI font size
  • Additional "\" character is added to the destination file path if the resulting file type is changed on the "Export results" dialog
  • The "NullReferenceException" error is encountered on generating undo SQL script for a database containing BLOB values using the CLI
  • Excessive GO keyword is added to end of undo and redo scripts in specific cases
  • The application stops responding for a significant time when exporting transactions from a large database to HTML file consuming all available CPU and RAM resources
  • Exporting to HTML takes too long for specific database
  • The "System.AccessViolationException" error is encountered when exporting results to HTML for specific database
  • The application fails to retrieve the server-side components (SSC) status information for SQL Servers where old SSC version was uninstalled
  • The application fails to connect to SQL Server to retrieve server side logs with "The certificate chain was issued by an authority that is not trusted." in case "(local)" is used instead of SQL Server name or IP address
  • An undo script created via the CLI contains no data in case changes made in specific time period are audited
  • The server-side component tries to use wrong online transaction log file
  • The auditing process stops after few operations returned when auditing SQL Server 2000 database when the "Server usage" option is On
  • Wrong message displayed when trying to connect to the unsupported SQL Azure server
  • The "/html" CLI switch does not work correctly
  • The "Unexpected error occurred" error is encountered when the project file created for one database is used with another one using the CLI with "/d" switch
  • The "Next" button in the last step in the server-side components installation process is obsolete
  • Aborted transactions referenced incorrectly in the "Statistics" dialog
  • Wrong text in the "Others" section of the "Schema objects" filter group
  • The term previously searched with low caps cannot be retyped with upper caps using the "Find" feature
  • The "Uncheck all" option is disabled when a filter is applied after checking transactions
  • Column headers doesn't have describing tooltips
  • The dialog warning the user that SPID value has to be between 0 and 65535 cannot be closed by pressing the Enter key
  • If the number of records is reduced by applying the filter, the selected record number is larger than the total number of records
  • The information about the loaded project is missing until the "Processing logs" progress bar dialog is closed
  • The "Statistics" dialog shows no data until reading process is finished, even if the resulting grid contains data
  • The transactions are not filtered correctly using the "Time range" filter when creating an undo script via the CLI, or exporting the results directly into an undo file
  • The "Check prerequisites on target server" error is encountered when attempting to connect to a SQL Server installed on a system with Data Execution Prevention (DEP) turned on, or on a system where its hardware ID is changed
  • The "Connection to the < databasename > on the server < hostname > failed." error is encountered when attempting to connect to any SQL Server instance if the application is running on Windows XP or on Windows Server 2003
  • Changes:
  • Server side components are not necessary when auditing a local database
  • The application stores all server-side log files and metadata in "C:\ProgramData\ApexSql\ApexSqlLog\(local)\LOG" folder
  • Redesigned "Find" dialog to improve usability - "First N hours" from data sources and "Last N hours" from data sources
  • Added standard row navigation commands at the bottom of the resulting grid
  • Removed connection monitor functionality

New in ApexSQL Log 2011.03.1092 (Jun 4, 2013)

  • Fixed:
  • The "Connection to the < databasename > on the server < hostname > failed." error is encountered when attempting to connect to any SQL Server instance if the application is running on Windows XP or on Windows Server 2003

New in ApexSQL Log 2011.03.1091 (May 27, 2013)

  • The "Check prerequisites on target server" error is encountered when attempting to connect to a SQL Server installed on a system with Data Execution Prevention (DEP) turned on, or on a system that’s had its hardware ID changed

New in ApexSQL Log 2011.03.1090 (May 18, 2013)

  • The "Check prerequisites on target server" error is encountered when attempting to connect to a SQL Server installed on a system with Data Execution Prevention (DEP) turned on, or on a system that’s had its hardware ID changed

New in ApexSQL Log 2011.03.1089 (Apr 20, 2013)

  • The transactions are not filtered correctly using the time-range filter when creating an undo script via the CLI, or exporting the results directly into an undo file

New in ApexSQL Log 2011.03.1088 (Apr 20, 2013)

  • Enhancements:
  • The application now provides information on the limitations of the trial version when running in trial mode
  • Fixes:
  • If a field value filter is added to a project, the table columns initially labeled as CLUSTERED in the Operation details tab of the Results grid, will not be shown after re-running the same project

New in ApexSQL Log 2011.03.1087 (Apr 20, 2013)

  • The "System.PlatformNotSupportedException" error is encountered when the application is running on Windows XP and a full database backup is added

New in ApexSQL Log 2011.03.1086 (Apr 20, 2013)

  • Update operations can’t be reconstructed when a database is restored from a backup and multiple sets of full database and transaction log backups are used as additional data sources
  • Some operations are not detected when the latest transaction log backup, created prior to a full database backup from which the database has been restored, is used as an additional data source

New in ApexSQL Log 2011.03.1084 (Apr 20, 2013)

  • The "hexadecimal value 0x07 is an invalid character" error is encountered when exporting data to HTML

New in ApexSQL Log 2011.03.1083 (Dec 27, 2012)

  • Fixes:
  • Depending on the data size, up to 20 operations from the first segment of the transaction log are skipped when reading multiple sets of full database and transaction log backups stored in the same backup file
  • The "hexadecimal value 0x0E is an invalid character’’ error is encountered when exporting data to HTML

New in ApexSQL Log 2011.01.1039 (Dec 29, 2011)

  • Enhancements:
  • Application now supports auditing of SQL Server Denali CTP3 databases
  • Application now fully supports auditing of the following SQL Server Denali CTP3 DDL operations:
  • CREATE/ALTER/DROP SEQUENCE
  • CREATE/ALTER/DROP TABLE … AS FILETABLE
  • CREATE/DROP COLUMNSTORE INDEX
  • Application will now run as 64-bit process under 64-bit OS
  • Server Activation Center dialog has been redesigned for improved usability
  • Connection Monitor Manager dialog has been redesigned for improved usability
  • Application stability has been improved when auditing larger than 32 GB transaction logs
  • Memory consumption has been improved when auditing transaction logs larger than 2 GB by preventing memory overuse
  • Performance has been improved by 40% when auditing transaction logs with more than 1,000,000 operations
  • Auditing of page and row compressed tables is now supported
  • Auditing of SPARSE columns is now supported
  • Application can now reconstruct changes made with SELECT INTO statements
  • Application can now reconstruct changes to numeric data stored in the vardecimal storage format
  • Application can now be started without requiring administrative privileges
  • User feedback dialogs have been updated for improved usability
  • Fixes:
  • Incorrect database version is shown in status bar tooltip for SQL Server 2000 databases
  • Mapped table doesn't exist in database.” error is encountered on editing or refreshing currently opened project when previously mapped table is deleted
  • Application prompts to install already installed Server Side Components if the connected user has insufficient privileges
  • Old table ID mapping doesn't work when transaction log processing is performed on the server with Server Usage option set to either ON or AUTO
  • Application requires administrative privileges to start
  • Connection Monitor Manager dialog is closed after any warning/error message not allowing fixing issue right away
  • Application doesn’t offer to install Server Side Components when sending server logs from a server with no Server Side Components installed
  • Export type option is always set to Output transactions and operations info into | XML file when editing project
  • Offline databases are displayed in database picklist on Connect to database tab of Project settings form
  • no_header switch doesn't suppress outputting header for SQL export type in CLI
  • DATETIMEOFFSET values are scripted incorrectly into UNDO/REDO scripts
  • Update operations on BLOBs may be scripted twice into UNDO/REDO scripts
  • Changes:
  • Server Side Components of all older versions will now be uninstalled from the server when installing a newer version
  • Progress dialogs have been updated to be more standard with other applications
  • Old and New Value comparison results in Column Data Viewer for UPDATE operations have been replaced with individual values

New in ApexSQL Log 2010.02.1004 (Jul 29, 2011)

  • Enhancements:
  • Application now fully supports auditing of the following DDL operations:
  • CREATE/DROP SCHEMA
  • Progress dialogs have been redesigned across the application for improved accuracy and usability
  • Server Side Components can now be uninstalled through Server Activation Center dialog
  • Connection Monitor Manager dialog has been redesigned for improved usability
  • Performance of UPDATE reconstruction has been improved for rarely updated rows (up to 400% depending on internal state of the operation)
  • Performance of data export has been improved up to 100% for BLOBs larger than 64 Kb
  • The following new switches have been added to CLI:
  • ifl [/intermediary_files_location] – Specifies location of intermediary files created during auditing
  • Delay in opening Filter step of Connection Wizard with lots of hosts, applications or user data has been eliminated
  • Amount of memory required for UPDATE reconstruction has been reduced by 10% on average
  • Fixes:
  • GUI gets unresponsive when auditing with Server Usage option ON
  • System.InvalidOperationException exception is encountered when opening a project if ‘System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing’ security setting is enabled either in the Local Security Policy or as part of Group Policy
  • Searching through main grid with more than 100,000 operations results in System.NullReferenceException exception
  • ALTER PROCEDURE operations are not detected
  • Send Logs ribbon command does nothing if default email client is already opened
  • Select All Operations in This Transaction main grid context menu command selects incorrect operations in main grid with more than 100,000 operations
  • Operation Details, Row History, Undo Script, Redo Script and Transaction Information tabs show nothing if there’s only 1 operation in main grid
  • Export type settings get restored from projects incorrectly in GUI
  • Credentials used for accessing Connection Monitor with Connection Monitor Manager dialog aren’t persisted between sessions
  • System.ArgumentOutOfRangeException exception is encountered when scrolling main grid with more than 100,000 operations extracted from SQL Server 2000 transaction log
  • Backups don’t get specified in sample CLI command when exporting auditing results with backups among data sources
  • Changes in Date/time range filter get incorrectly reflected in sample CLI command shown when exporting auditing results
  • Comparison with NULL in Field values filter results in incorrectly formatted /fields switch argument in sample CLI command shown when exporting auditing results
  • "Switch 'css' is not recognized" error is encountered when executing sample CLI command generated for exporting auditing results to HTML
  • "SSA exception:" error is encountered when auditing remote SQL Server 2008 R2 instances with Server Usage option ON
  • Value does not fall within the expected range” exception is encountered in CLI if /fields switch argument contains LIKE operator
  • Searching in Operation Details grid works incorrectly with more than 100,000 operations in main grid
  • "Trusted connection will be used" message gets outputted twice in CLI if /trusted switch was specified
  • Filter Converter doesn’t warn if specified file is of bad format
  • Textual data cannot be copied from Column Data Viewer
  • Corrupted Connection Monitor tables can cause performance degradation (up to 2 times and more)
  • Default Intermediary Folder application option can’t be set in CLI
  • Copy Rows to Clipboard ribbon command does not work if main grid is not focused
  • Usage of deprecated CLI switches /ddl, /undo_ddl, /include_dropped_tables, /exclude_system_tables, /include_dropped_users, /include_unknown_applications, and /include_unknown_clients does not result in warning
  • Column Data Viewer does not show binary data
  • Show filter row main grid context menu command does not work
  • Create Undo Script and Create Redo Script main grid context menu commands get disabled with more than 100,000 operations in the grid if all are selected
  • Values of TEXT data type are shown in hexadecimal form in Row History grid
  • Application cannot detect whether Server Side Components are already installed if connected user has insufficient permissions on the extended stored procedures installed as part of Server Side Components

New in ApexSQL Log 2010.01.0979 (Jul 29, 2011)

  • Enhancements:
  • All transaction log processing can now be done on the server with only results sent to the client
  • Depending on the case auditing performed on the server can significantly improve overall performance vs auditing performed locally on the client (from 10% to more than 400%)
  • Server Usage options group has been added to Options dialog to control whether to perform auditing on the server. Available choices are Off (default), On and Auto
  • Application now fully supports auditing of the following DDL operations:
  • CREATE/ALTER/DROP TABLE
  • CREATE/ALTER/DROP FUNCTION
  • CREATE/ALTER/DROP PROCEDURE
  • CREATE/ALTER/DROP TRIGGER
  • CREATE/ALTER/DROP VIEW
  • CREATE/DROP CHECK CONSTRAINT
  • CREATE/DROP DEFAULT
  • CREATE/DROP DEFAULT CONSTRAINT
  • CREATE/DROP FOREIGN KEY
  • CREATE/DROP INDEX
  • CREATE/DROP PRIMARY KEY
  • CREATE/DROP RULE
  • CREATE/DROP STATISTICS
  • CREATE/DROP TYPE
  • GRANT PERMISSIONS
  • RENAME OBJECT
  • REVOKE PERMISSIONS
  • Encrypted SQL Server objects get fully decrypted in auditing of DDL operations
  • DML and DDL operations can now be shown in grid with different background colors
  • Main grid can now display any number of operations
  • Application now supports filtering by Unknown transaction state
  • The following predefined filters have been added to Time range filter of Project wizard: "Whole transaction log", "Last 30 days", "Last 7 days", "Last 24 hours", "Last 60 minutes"
  • Each column on Columns filter step of Project wizard has appropriate tooltip
  • Parent Object’ and ‘Parent Schema’ columns have been added to Main grid
  • New Office 2007 style interface with ribbon bar, quick access toolbar, and ApexSQL Log button has been introduced
  • New Resources ribbon bar has been introduced for quick access to Help page, Support forum, Training page, FAQs, Knowledge base, Troubleshooting, About and Get Updates dialog boxes
  • Filter files have been replaced with full-fledged projects
  • New standard Project Management dialog has been introduced
  • Project Management dialog now shows recently used projects or projects stored in any folder of choice
  • Projects can be Pinned/Un-Pined to Recent Projects list on Project Management dialog
  • Project description can be edited directly from Project Management dialog
  • Show on Startup' option has been added to Project Management dialog box
  • Startup Action options group has been added to Options dialog to control Project Management dialog behavior. Available choices are 'Show Project Management dialog', 'Show last opened project' and 'None'
  • Advanced button implemented in Project wizard displays additional steps (Database Backups, Old Table ID Mapping)
  • Filter converter has been implemented for converting old (ApexSQL Log 2008) filter files to new projects
  • Filter Defaults for Transactions, Operations and Other filters have been added to Options dialog
  • Specific backup sets can now be used as a data source
  • Exporting to SQL BULK format is now available from the ribbon in the form of "Export to SQL BULK" command
  • Server Activation Center dialog has been redesigned for improved usability
  • Main window Status bar has been redesigned and now shows numbers of checked and excluded by filter rows in addition to server and database names
  • New Comparison Statistics dialog is shown in response to clicking on checked or excluded by filter bars of main windows Status bar
  • New tooltip balloon has been added to data source bar of main window Status bar
  • Options dialog has been redesigned with new Office 2007 button bar
  • Application can now be presented in 3 color schemes: Blue, Silver and Black
  • Field Filter Editor has been redesigned and now supports accurate numeric comparison and nested conditions
  • New Field Filter Editor allows to filter operations based on 'Exclude if' or 'Include if' conditions
  • New Field Filter Editor criteria can use the following comparison operators: 'Equal', 'Not Equal', 'Between', 'Not between', 'Contains', 'Not contains', 'Begins with', 'Ends with', 'Any of' and 'None of' and the following logical operators: 'And', 'And not', 'Or' and 'Or not'
  • Installing server-side components remotely now doesn’t require administrative shares on the remote server (requires membership in the sysadmin server role)
  • UPDATE reconstruction has been improved and now covers even more edge cases which results in improved accuracy of auditing trail
  • GO commands are inserted every few transactions in SQL scripts
  • The following connection options have been added to Connection step of Project wizard and Connection Monitor Manager login form: 'Connection timeout', 'Execution timeout' and 'Encrypt connection'
  • Old Table ID mappings information is now displayed in CLI
  • Online transaction logs and available database backups are now identified faster (proportionally to their count)
  • The following new switches have been added to CLI:
  • eut [/exclude_user_tables] - Excludes all user tables from auditing,
  • ist [/include_system_tables] - Includes system tables in auditing,
  • edt [/exclude_dropped_tables] - Excludes operations made on dropped tables,
  • edu [/exclude_dropped_users] - Excludes operations made by dropped users,
  • eua [/exclude_unknown_applications] - Excludes operations made by unknown applications,
  • euc [/exclude_unknown_clients] - Excludes operations made by unknown clients,
  • ssa [/server_side_auditing] – Specifies server usage mode
  • pr [/project] – Specifies path to project file
  • Fixes:
  • Server-side components can’t be installed on Windows Vista/2008 Server/7 with User Account Control (UAC) on
  • Exception occurred while flushing data: Timeout expired” error accompanied by Connection Monitor stoppage is logged into application log
  • "SqlDateTime overflow. Must be between 1/1/1753 12:00:00 AM and 12/31/9999 11:59:59 PM." error is shown on attempt to audit detached log files from different databases at the same time
  • User tables aren’t selected by default on Tables step of Filter wizard
  • SQL Server service shuts down if installation of server-side components fails
  • System.UnauthorizedAccessException exception is encountered in case default output folder is no longer accessible
  • "QueryDosDevice() failed - Access is denied" error is logged into application log in case SQL Server service is running under built-in ‘Network Service’ account
  • ExecQuery failed: Unknown exception occurred” error is logged into application log on installation of server-side components in case the account SQL Server is running under has no EXECUTE permissions on xp_ApexSqlLog2008 or xp_ApexSqlLogApi2008 extended stored procedures
  • Server-side components cannot be uninstalled from local SQL Server 2008 instance under Windows Authentication
  • Available transaction log backups are not shown automatically on Data Sources step of Log Selection wizard
  • Incorrect DBCC statement” error is encountered on install if selected SQL Server account has insufficient permissions
  • Application cannot upgrade server-side components when it fails to check SQL Server account permissions
  • Application is unable to read SQL Server 2005 transaction logs on SQL Server 2008
  • Filters specified in Filter Field Editor don’t work for TEXT fields
  • Images stored in BLOB fields are not rendered as such on Row Details tab
  • users CLI switch is case-sensitive
  • Processing progress isn’t updated for exports from Main grid
  • System.OutOfMemoryException exception is encountered when creating REDO/UNDO scripts for very large (>100M) BLOB fields
  • Inequality operators (>, and 1M operations
  • External component has thrown an exception” error is encountered when auditing SQL Server 2005 databases with >2G BLOB fields
  • Changes:
  • The following CLI switches have been deprecated:
  • idt [/include_dropped_tables],
  • est [/exclude_system_tables],
  • idu [/include_dropped_users],
  • iua [/include_unknown_applications],
  • iuc [/include_unknown_clients],
  • ddl [/ddl],
  • ud [/undo_ddl],
  • mt [/mapped_tables]
  • Server-side components are no longer installed in SQL Server's Binn directory except for extended procedures dll which has to be installed there due to limitations of SQL Server
  • When activated for DDL operation Operation Details tab displays list of constituent operations performed on system tables
  • Old Table ID Mapping does not support mapping to IDs of system tables anymore
  • Server explorer panel has been deprecated
  • Connection wizard has been redesigned and merged into Project wizard
  • Table’ column has been renamed to ‘Object’ in Main grid
  • Regular Help button has been replaced with question mark button in title bar on all dialogs and windows
  • Operations CLI switch (/ops [/operations]) now accepts DDL operations
  • Number of operations to show’ Transactions filter option has been removed. Now everything that passes filter is outputted
  • The following options have been removed from Descriptions filter:
  • Show 'SplitNext' Transactions,
  • Show 'Allocate Root' Transactions,
  • Show 'Split' Transactions,
  • Show 'ShrinkFile' Transactions,
  • Show 'MoveIndexPage' Transactions

New in ApexSQL Log 2008.06.0838 (Mar 25, 2010)

  • Fixes:
  • Server-side components installation fails on Windows Vista/7 with UAC turned ON
  • Server-side components installation fails if the application extended stored procedure DLL (ApexSqlLog2008Xprocs.dll) is locked by SQL Server
  • In rare instances, SQL Server service stops when installation of server-side components fails because UAC is ON for Windows Vista/7 and/or the application extended stored procedure DLL (ApexSqlLog2008Xprocs.dll) is locked by SQL Server
  • In rare instances, data in columns that have a BLOB data type are not displayed in grid results, UNDO/REDO scripts, or in other export formats
  • Transaction log reading is unnecessarily extended beyond limits specified in time range filter causing unnecessary slowdowns during auditing
  • In rare instances, no information is displayed in Row Details grid or in export files for Update operations
  • When installing server-side components in Windows XP and when the SQL Server service is running under a Network Service account, a login dialog is sometimes unnecessarily displayed
  • Changes:
  • The following new messages can now be shown during installation and execution of server-side components:
  • Insufficient permissions to execute server-side components. Please make sure SQL login used has EXECUTE permission on ApexSQL Log extended procedures (ApexSQLLog2008XProcs.dll).
  • Insufficient permissions to install server-side components. Please make sure you're a member of the sysadmin server role.
  • Insufficient credentials to install server-side components. Please check user name, password and/or domain name

New in ApexSQL Log 2008.05.0834 (Mar 25, 2010)

  • Enhancements:
  • Application is now able to export auditing results to HTML format
  • Auditing intermediary files storage can now be configured via the new Default Intermediary Directory option. Intermediary files include transaction log metadata cache as well as application log files
  • The following new switches have been added to CLI:
  • /intermediary_files_location - specifies location for intermediary files created during auditing
  • /html - specifies the name of the HTML export file
  • New "Send client and server-side logs" menu item is added to Help menu. If no email client is installed, the client-side logs folder is opened
  • Connection Monitor can now be configured via the new Connection Monitor Manager form available from Tools menu
  • BLOBs containing images are now rendered as such in Row History grid for SQL Server 2005 and 2008
  • BLOB reading now consumes less memory (up to 50% less)
  • Fixes:
  • Connection Monitor is not started after installation
  • Create Undo/Redo Script main grid's popup menu items are disabled for selected row
  • Checking "Show system tables" option also checks user tables in Log Filter wizard
  • In-row filters aren't applied to main grid rows that were previously checked or unchecked
  • Special symbols (e.g. '-', '\', etc.) can be added into SPID filters in Log Filter wizard
  • Executing the “Auto Resize Columns” command from the tool button does not do the same thing as executing it from the main grid’s context menu
  • Toolbars contain unnecessary whitespace
  • Database backups have no associated icon on Select Backups step of Log Selection wizard
  • Not all available values are displayed on main grid’s in-row filter
  • No warning is shown if date input in /to switch is greater than the date in /from switch in CLI
  • Column Data Viewer is always empty for UPDATE operations if the client is operating under an operating system with Korean locale
  • Application doesn't support paths with Cyrillic characters
  • It's impossible to connect to SQL Server with Windows Authentication under Vista with active UAC
  • Log Filter wizard always shows transaction logs from last opened database vs the current database that the user is connected to
  • Hiding the in-row filter hides all rows from the main grid
  • The /fs switch is incorrectly described in the CLI help file
  • System.Exception exception is encountered if the account used for auditing doesn’t have SELECT permission on the mssqlsystemresource SQL Server 2005/2008 database
  • Transaction log backups are incorrectly shown on Select Database Backups step of Log Filter wizard
  • Server-side components installed during application are not uninstalled when client is uninstalled
  • "Export Checked As" command executed from its corresponding toolbar button or from the main grid’s context menu exports all columns from the main grid instead of exporting the selected/displayed columns only
  • Exporting to XML fails if initiated from the Log Filter wizard
  • When a machines' hardware ID changes, the server's activation status becomes invalid and re-activating is not possible
  • The application exports column values incorrectly
  • When generating REDO scripts, a System.OutOfMemoryException exception is sometimes encountered
  • "Unknown SQL Server version" error is received when reading SQL Server 2000 backups
  • Inaccessible transaction logs and database backups are still shown as data sources in Log Selection wizard
  • Chinese characters aren't shown on the main grid
  • NULL values are incorrectly exported as empty strings when the selected output is SQL BULK files
  • BULK import error is received when running an SQL BULK script with very large BLOBs
  • Very large BLOBs may cause application failures when being outputted to file
  • The larger result set is populated to the main grid the slower the populating is
  • Online transaction log files cannot be accessed sometimes on an x86 OS that has more than 4 GB of RAM
  • BLOB exporting consumes more memory than it should
  • Clustered indexes with variable-length columns are incorrectly outputted for SQL Server 2005 and 2008
  • Variable-length column values are incorrectly outputted for SQL Server 2005 and 2008
  • SPID values are incorrectly outputted for SQL Server 2008
  • SMALLMONEY values are outputted incorrectly
  • The application doesn’t output all BLOBs found in data sources
  • UPDATE operations are sometimes not reconstructed correctly even when there is enough data to do so
  • BLOBs whose data type has been changed are outputted incorrectly
  • The application fails when it tries to output an invalid XML found in provided data source
  • Online transaction log and database files hosted on Windows 2000 cannot be read
  • REDO/UNDO scripts are incorrectly generated for tables with IDENTITY columns
  • The application fails when trying to read SQL Server 2000 database backups
  • Servers with expired evaluation can’t be activated
  • REDO/UNDO scripts are incorrectly generated for operations affecting new SQL Server 2005 BLOB types (e.g. varbinary(max), varchar(max), etc.)
  • Connection failure is received when application attempts to read a non-existing online file
  • Non-UNICODE multi-byte characters are exported incorrectly
  • Operations in UNDO scripts generated from the main grid are not scripted in reverse order
  • Operations in XML/CSV/HTML exports generated from the main grid aren't sorted the same as in the main grid
  • Unspecified exception is encountered when connection is lost during analysis
  • “The System cannot find the file specified” error is encountered when installing server-side components on SQL Server 2000 for the first time
  • System.AccessViolationException exception is encountered when selecting Row History tab for an operation on SQL Server 2000 table with BLOB columns
  • "Object reference not set to an instance of an object" error is encountered when exporting results from the main grid grouped by a column
  • Uninstalling application doesn't uninstall server-side components from the local server they have been installed on during installing
  • Date/Time filters sometimes return nothing instead of appropriate data
  • Margins are not saved in Preview Grid form
  • Maximize icon is missing in Preview Grid form
  • Unnecessary comma is outputted when exporting from the main grid in SQL Script format
  • CSV exports have no corresponding note in the header when the application is in evaluation mode
  • Operation times are outputted without quotation marks (‘) when exporting from the main grid in SQL Script format
  • Summary form shown on analysis completion sometimes reports total number of rows processed incorrectly
  • The /append CLI switch doesn't append analysis results to the specified file
  • The /verbose switch isn’t described in the CLI help output
  • “General network error” exception is encountered when selecting row in the main grid if connection with server is lost
  • "Uncheck All" command is disabled in the main grid's context menu when checking rows from Find form
  • Script path isn’t shown on Output Options step of Log Filter wizard on attempt when generating UNDO/REDO script right after SQL BULK files
  • Selected custom script editor doesn’t open if there’re spaces in the path to its executable
  • The application queries all database tables disregarding the specified table filter in CLI
  • Changes:
  • Server-side components have been split to two independent sets: server-side components for ApexSQL Log and server-side components for ApexSQL Recover. On upgrade, un-used server-side components are deleted.
  • Split ApexSqlServerXprocs2008.dll into ApexSqlLog2008Xprocs.dll and ApexSqlRecover2008Xprocs.dll
  • Split ApexSqlServerHelper2008.exe into ApexSqlLog2008ServerHelper.exe and ApexSqlRecover2008ServerHelper.exe
  • Split ApexSqlServerHelper2008.sys into ApexSqlLog2008ServerHelper.sys and ApexSqlRecover2008ServerHelper.sys
  • Renamed ApexSqlConnectionMonitor2008.exe to ApexSqlLog2008ConnectionMonitor.exe
  • Renamed xp_ApexSqlConnectionMonitor2008* extended procedures to xp_ApexSqlLog2008ConnectionMonitor*
  • Renamed sp_ApexSqlConnectionMonitor2008* stored procedures to xp_ApexSqlLog2008ConnectionMonitor*
  • All server-side logs for the application's server-side components are consolidated into one log file: ApexSqlLog2008.log
  • The following error messages have been replaced with more informative equivalents:
  • "Unknown error code: 128 during activation"
  • "ApexSqlServerHelper2008 failed: OpenSCManager() failed: Access is denied. (error code = 5)"
  • "Copy file for ApexSqlServerXprocs.dll failed: The system cannot find the path specified. (error code = 3)"
  • "Cannot access transaction log file"
  • "CreateService() failed: The specified service has been marked for deletion"
  • "ApexSqlServerHelper2008 failed: log2::lnhf::GetFileDeviceName: Access is denied."
  • "System.OutOfMemoryException"
  • All application logs, both client and server-side, are now in UNICODE
  • Evaluation period for each server has been changed from 30 to 14 days
  • New Activation Error form has been added to the application and will automatically be shown when an activation error occurs. This new form is more informative and simplifies the reporting of activation errors

New in ApexSQL Log 2008.03.0716 (Mar 25, 2010)

  • Enhancements:
  • Column filtering is now available for file outputs in both GUI and CLI
  • Application now reports analysis progress in more details
  • The following new switches have been added to CLI:
  • /transform_xsl - applies XSL transformation to XML export
  • /export_columns - specifies columns to export
  • /argfile - specifies argument file (used to reduce the number of switches specified)
  • /console_width - sets output console width
  • /force - ovewrites existing file with same name
  • /out_to - redirects console output to specified file
  • All CLI switches now have shorter versions/aliases (e.g. /transactions switch now has /tr alias)
  • Main grid performance was improved for large amounts of data (50+K operations) by approximately 70%
  • Fixes:
  • Log Selection Wizard displays the same backup file multiple times if the backup file was used multiple times by the original database for backup
  • Errors in CLI calls, including typo errors, aren't reported
  • After main grid is refreshed, the first mouse click over the grid doesn't select anything
  • Backup selections are not remembered between sessions in the Log Selection Wizard
  • Progress indicator doesn’t move for any of text exports
  • Progress bar is not shown for UNDO script generating in the details pane
  • Backup files existence isn't checked prior to analysis
  • Not all operations are shown in the main grid for SQL Server 2008 transaction logs
  • Uninstaller doesn't remove server-side components from server
  • /D switch doesn't work if it's specified after /B switch and vice versa
  • Unicode symbols are shown incorrectly in the Data viewer dialog
  • Exception if user generates script to output folder via CLI without write permissions
  • Application does not process databases having names with special characters (e.g. "Master's")
  • Installation of server-side components after auto-updating from previous major version fails
  • On the initial use, application is opened with non-default options
  • /backup CLI switch can't find backups in current folder
  • Alt + "hot key" doesn't work in Log Filter Wizard
  • Changes:
  • /login CLI switch renamed to /user
  • /include_unchanged_fields CLI switch renamed to /export_unchanged_fields
  • /detached CLI switch alias (/d) renamed to /dt

New in ApexSQL Log 2008.02.0708 (Mar 25, 2010)

  • Enhancements:
  • Application can now read BLOBs from transaction logs
  • Transaction logs contents can now be outputted directly to file from GUI (UNDO and REDO scripts, XML, CSV, SQL and SQL BULK exports)
  • New Column filter step in Log Filter Wizard allows user to select which columns to output to grid
  • New Summary step added to Log Filter Wizard to show number of retrieved records
  • All grids in Log Filter Wizard now have standard context menus
  • Undo and Redo Script tabs now have standard context menus
  • HyperBac files can now be used as database backup sources
  • XML exports now include export start and finish times
  • /export_unchanged_fields switch was added to CLI
  • Table filtering performance was significantly improved (especially for rarely updated tables); performance improvement can vary
  • Fixes:
  • Not all logged operations are shown when reading SQL Server 2008 transaction logs
  • Application incorrectly recognizes local SQL Server cluster, treating it as remote server, causing performance issues
  • Application can't connect to local instances of SQL Server 2008 using "(local)" in server field
  • Unknown field names appear in REDO DDL scripts under SQL Server 2005
  • Patterns don't work on Tables step of Log Filter Wizard
  • SQL Server 2000 databases may contain "Schema" instead of "Owner" in application labels
  • Sorting and grouping by empty item are allowed in Sort and Group By forms
  • Database connection remains open after analysis is finished in GUI
  • Table ID may not be shown in operations grid
  • Log Filter may not be saved if it was opened for editing
  • Old Activation form may show up at application start-up
  • Activating application with Alt+Tab may result in exception
  • Search progress bar and status bar may show different number of operations
  • Column data viewer window is not modal
  • Database backups may not be shown in Server Explorer
  • Double-click on backup transaction log in Server Explorer may result in online transaction log being selected in Log Selection Wizard
  • "Local attribute name cannot be empty" error appears when trying to analyze "" db
  • Group By area is shown for all analysis windows by default
  • Tables cannot be filtered by checked state on Tables step of Log Filter Wizard
  • Row Details tab doesn't show user data types
  • REDO and UNDO DDL scripts are empty for any database under SQL Server 2008
  • Activation form is shown on attempt to uninstall server-side components from non-existing server
  • "Check All" button in Find form does nothing
  • Operations' check state can't be changed with Space button in operations grid
  • Clear All Column Filters command works incorrectly when activated from context menu
  • Collapse/Expand items in context menu of Server Explorer are always enabled
  • Changing server in Log Selection Wizard changes selected database picklist item from "" to ""
  • Application stops working when exiting using File | Exit
  • Log analysis can't be cancelled with Cancel button on progress form
  • Filtering by UNKNOWN tables works incorrectly
  • Horizontal scroll bar is missing in Log Selection Wizard
  • Filtering by dropped tables doesn't work when database does not contain tables
  • Operation type (INSERT, UPDATE or DELETE) can be changed in operations grid
  • Link for Support Forum program group in Help | ApexSQL Online | Online Support menu is incorrect
  • Changes:
  • Transaction log reading is now done in the natural order of operations and not based on the end-of-transaction time
  • Grid toolbar is hidden by default
  • Icons were removed from Transactions filter in Log Filter Wizard

New in ApexSQL Log 2008.01.0609 (Mar 25, 2010)

  • Enhancements:
  • Added support for reading SQL Server 2008 transaction logs (MAJOR ENHANCEMENT)
  • Added support for new SQL Server 2008 types (MAJOR ENHANCEMENT):
  • DATE, DATETIME2, DATETIMEOFFSET, TIME, HIERARCHYID, GEOMETRY, GEOGRAPHY
  • Added database backups as optional source of auditing data (MAJOR ENHANCEMENT)
  • Added support for COLLATE and code pages in auditing and recovery (MAJOR ENHANCEMENT)
  • Improved scalability when working with very large transaction log files by an order of magnitude (MAJOR ENHANCEMENT)
  • Improved general auditing performance by approximately 25%
  • Added support for filtering uncommitted transactions
  • Added support for in-row values of XML data type
  • Added integrity check for server-side components
  • Added tabled IDs to CREATE/DROP TABLE statements
  • Added new button to main toolbar to change log filter settings
  • Added Summary dialog after log is processed
  • Improved statistics logging for queries and global memory
  • Improved Table ID mapping dialog for easier to use
  • Fixes:
  • Performance problem when reconstructing updates on tables with clustered indexes.
  • A problem with transaction log reading.
  • A minor problem with application's finalization.
  • A minor problem with logging.
  • A problem with MONEY and SMALLMONEY formatting.
  • Filtering Using Table Row Data.
  • There is no hotkeys for 'Executable' and 'Arguments' edits in Options dialog.
  • Quotation marks for path to other editor in Log option are added.
  • Current Row Panel can be closed but can't be opened again.
  • Row grid is cut off.
  • Exception raises if try to open Diff window for Update records.
  • “NullReference” Exception encountered when re-opening log result rows as a new view
  • Existing Filter file path field loses its focus after entering any character
  • Log Selection for DB leads to the empty tree node in the Server explorer
  • Cannot connect to local SQL Server 2008 server
  • Changes:
  • Separated toolbar items into Grid, File, and Result
  • Moved application log and other temporary application files from "Program Files" to user's own directories
  • Removed file naming tags from Options dialog
  • Moved all items from Exports context menu to Results menu
  • Moved all items from Grid menu to Results menu
  • Reorganized controls from Tables step of Log Filter Wizard
  • Controls for picking time range in Log Filter Wizard moved to Transactions node
  • The functionality of the Recovery Wizard of ApexSQL Log has been moved to a new product, ApexSQL Recover.
  • SPID fields are edited with a new dialog
  • Description filters in Log Filter Wizard are edited in grid
  • Removed navigation buttons from main toolbar
  • Removed "Save As", "Reset" and "Defaults" buttons from Log Filter Wizard
  • "Operations" node in Log Filter Wizard is renamed to "Transactions"
  • Controls on "Transactions" page of Log Filter Wizard are rearranged
  • "Current operation" panel is moved to Log form and renamed to "Transaction Information".
  • "Open Logs" node in Server Explorer is removed

New in ApexSQL Log 2005.11.0534 (Mar 25, 2010)

  • Enhancements:
  • Improved transaction log reading performance.
  • Added reading of transaction logs for February CTP of SQL Server 2008.
  • Fixes:
  • A problem with UPDATE reconstruction when row has versioning info data (MAJOR FIX)
  • A problem with row reading when row has versioning info data (MAJOR FIX)
  • A problem with UNDO statements not being output in reverse.
  • A problem with clustered indexes with more than one variable length column.
  • A problem with UPDATE reconstruction when analyzing databases created on SQL7/2000 but now hosted on SQL 2005/2008.
  • A problem with passing through invalid rows when field filtering is used.
  • Remove incorrectly logged messages during some recovery processes.
  • A rare problem with transaction log reading on SQL Server 2005/2008.
  • A rare problem with transaction log reading on SQL Server 2005/2008 with databases upgraded from SQL Server 7/2000.
  • A rare problem with tempdb getting blocked on SQL Servers with very high load level.
  • A rare problem with error message on databases with compatibility level 70.
  • Changes:
  • Moved application log and other temporary application files from "Program Files" to user's own directories.

New in ApexSQL Log 2005.10.0502 (Mar 25, 2010)

  • Enhancements:
  • Added support for ApexSQL Log API (MAJOR ENHANCEMENT)
  • Further improved quality of UPDATE reconstruction process (MAJOR ENHANCEMENT)
  • Added support for online transaction log reading on Vista 64-bit and Windows 2008
  • bit (MAJOR ENHANCEMENT)
  • Added experimental support for Itanium (IA64) platform for both SQL Server 2005 IA64 and
  • SQL Server 2000 64-bit.
  • Added experimental support for SQL Server 2008 on all platforms.
  • Added support for INSERT and DELETE operations affecting more than one row to auditing and exports.
  • (added "ROW_ORDINAL" to LOGNAV_RECORD table, "row_ordinal" tag to XML export and "Row Ordinal" to CSV export.)
  • Improved the performance of table, user name, application name and client host filtering.
  • Improved scaling for large auditing sets in GUI.
  • Improved overall scaling.
  • Added REDO/UNDO mark to REDO/UNDO scripts.
  • Added table existence check in DDL statemens in recovery scripts.
  • Added recovery of user defined data types from detached MDF files.
  • Fixes:
  • A problem when multiple transaction log backups are specified (MAJOR FIX)
  • Application stops working during exporting (MAJOR FIX)
  • A resource leak problem after auditing is finished affecting memory and other resources (MAJOR FIX)
  • A problem with Connection Monitor stopping to capture logins without restarting (MAJOR FIX)
  • A problem with BLOB recovery sometimes not working correctly when doing recovery from detached MDF files (MAJOR FIX)
  • A problem with online transaction auditing on Vista.
  • A problem with filtering of users retrieved uniquely by SID.
  • A problem with Connection Monitor when TCP/IP connections are disabled.
  • A problem with new user names, application names and client hosts filters not included
  • by default in the filter even when all names were previously selected.
  • A problem with invalid XML characters in XML output.
  • A problem with auditing read-only databases.
  • A warning messages in generated BULK scripts.
  • A problem with UPDATE operations logged due to change in table schema.
  • A problem with some UPDATE operations not being used in UPDATE reconstruction.
  • A problem with operations on forwarded stub rows passing through as data row operations.
  • A problem with not showing types of values in SQL_VARIANT fields.
  • A problem with resulting XML file when /no_header switch is specified.
  • A problem with resulting XML file when /append switch is specified.
  • A problem with status bar not updated when no operations are found.
  • A problem with no refresh of progress bar before first operation is found.
  • A problem with "Cancel" button being the default button in Recovery Wizard.
  • A problem with long-running server operations giving time-out error.
  • A problem with missing timestamp column value in WHERE clause of UNDO/REDO scripts even when it's part of PK/clustered index.
  • A problem with running Recovery Wizard from Server Explorer when using SQL Server authentication.
  • A problem with SQL Server authentication form demanding non-empty password.
  • A problem with transaction log backups sometimes not automatically offered by Log Selection Wizard.
  • A problem with showing user's SQL login name instead of NT user name when both have the same SID.
  • A problem with recovery of deleted rows from transaction logs when under evaluation.
  • A problem with connection "leak" in Recovery Wizard.
  • A rare problem with mixup of db ID, file ID and transaction log file names.
  • A rare problem with reconstruction of variable-length columns data.
  • A rare problem with output of tag in XML export.
  • A rare problem Connection Monitor not working on default SQL Server instances.
  • A rare problem with default server name in setup.
  • A rare problem with some transaction log operations not being loaded.
  • An unclear error message when accessing online transaction log files in SIMPLE recovery mode.
  • Various problems in error, warning and information messages.
  • Changes:
  • Renamed xp_ApexSqlLogMonitor_* extended procedures to xp_ApexSqlConnectionMonitor_*
  • Removed LOGNAV_RECORD2 primary key from LOGNAV_RECORD table and added LOGNAV_RECORD3 primary key.

New in ApexSQL Log 2005.04.0453 (Mar 25, 2010)

  • Enhancements:
  • Greatly improved reconstruction of UPDATE operations (MAJOR ENHANCEMENT)
  • Greatly improved memory footprint and performance scaling (MAJOR ENHANCEMENT)
  • Added support for recovery of VARCHAR(MAX), NVARCHAR(MAX) and VARBINARY(MAX) data types from
  • database files (MAJOR ENHANCEMENT)
  • Improved support for transaction log backups converted from 3rd party backups (MAJOR ENHANCEMENT)
  • Added partial reconstruction of changes made to fixed-length fields in UPDATE operations.
  • Added partial support for recovery of XML data type from database files.
  • Added support for reading SQL Server 7/2000 transaction logs under SQL Server 2005.
  • Added support for reading SQL Server 2005 transaction logs under SQL Server 7/2000.
  • Added more recovery reports details to recovery scripts.
  • Added dummy data to BLOBs that are partially recovered due to lack of data.
  • Added "row partially reconstructed" column to SQL, BULK, CSV and XML exports.
  • Added "/run_small" switch to command line interface which forces the application not to save
  • most of intermediate files on the hard drive. If there is less than 5% free space on the drive
  • the application will switch automatically to "run small" mode.
  • Added recovery script path selection to Recovery Wizard.
  • Added table mapping to MDF data recovery.
  • Improved generated recovery scripts for less-than-perfect data recovery scenarios.
  • Improved progress bar during transaction log reading.
  • Improved reliability of BLOB recovery algorithm.
  • Improved auditing performance in general.
  • Improved memory managment when under memory pressure.
  • Improved formatting for REAL and DOUBLE SQL types.
  • Improved diagnostic logging.
  • Integrated client-side and server-side setups into one setup.
  • Fixes:
  • A set of problems with server-side components running on SQL Server run by non-administrator account (MAJOR FIX)
  • A problem with relying on @@SERVERNAME for server name on repeated connections which
  • blocked re-connections for servers not accessible through their @@SERVERNAME (MAJOR FIX)
  • A problem with UPDATETEXT and line breaks in BLOB recovery (MAJOR FIX)
  • A problem with double reading of log files during open (MAJOR FIX)
  • A problem with recovery of some system table structures (MAJOR FIX)
  • A problem with primary key values in SQL export (MAJOR FIX)
  • A problem with XML data type recovery (MAJOR FIX)
  • A problem with some recovery options not working correctly on remote servers (MAJOR FIX)
  • A problem with putting server logs to system32 (or SysWOW64) directories. Now server logs are all in LOG
  • directory of SQL Server instance.
  • A problem with recovery of dropped tables in SQL Server 2000.
  • A problem with bad IDENTITY status for some reconstructed tables on SQL 2005.
  • A problem with grid refresh if the last transaction was rolled back.
  • A problem with clustered index keys not shown for un-reconstructed UPDATE operations.
  • A problem with in-row values in NTEXT fields not correctly shown.
  • A problem with recovery of BLOB data of NTEXT columns.
  • A problem with NVARCHAR(MAX) columns in recovered table structures.
  • A problem with some field values not being exported on UPDATE operations.
  • A problem with application stopping to work when trying to write to a read-only file.
  • A problem with "File not found" exception when doing recovery from online database files.
  • A problem with extended procedure connecting back to SQL Server and being rejected due to lack of permissions.
  • A problem with SQL authentication not working correctly when accessing logs from server tree.
  • A problem with SQL authentication if invalid user/password entered.
  • A problem with a label on SQL authentication user/password window.
  • A problem with relying on @@SERVERNAME to start Connection Monitor.
  • A problem with temporary UNDO/REDO scripts not having SQL extension.
  • A problem with table structure lines not ending with consistent UNICODE line endings.
  • A problem with reaching EOF of online database files.
  • A problem with declaration of FLOAT data type in generated scripts.
  • A problem with duplicate column names in some recovered table structures.
  • A problem with duplicate table names in some recovery scenarios.
  • A problem with lingering IDENTITY_INSERT state after a generated INSERT with identity fails.
  • A problem with inserting NULL field values into NON-NULL columns in some recovery scenarios.
  • A problem with application always demanding valid file paths in sysfiles.
  • A problem with recovery of tables with timestamp columns in some recovery scenarios.
  • A problem with duplicate servers in "Server Activation Center" dialog.
  • A rare problem with BLOB data updates being out of range for the current BLOB values.
  • A rare problem with not loading all operations in some circumstances.
  • A rare problem with command line interface not creating log files correctly.
  • A rare connectivity problem on SQL Server 2005.
  • A rare problem with activation not working correctly.
  • A rare problem with activations on multiple instances of SQL Server 2005.
  • A rare problem with NULL values causing application to stop responding.
  • A very rare problem with calls to some empty extended stored procedures hanging on SQL 2005.
  • A very rare problem with Connection Monitor not resetting on consecutive errors.
  • A very rare problem with ApexSQL Server Helper driver sometimes stopping to work on SMP machines.
  • Changes:
  • Increased drive usage for intermediate and temporary files during auditing/recovery, to approximately
  • % of transaction log file sizes. If there is less than 5% free space on the drive the application
  • will switch automatically to "run small" mode thereby saving on drive space.
  • Limited export options to exporting every 10th REDO/UNDO script during the evaluation period.
  • Limited copy to clipboard for all REDO/UNDO scripts during the evaluation period.

New in ApexSQL Log 2005.03.0417 (Mar 25, 2010)

  • Enhancements:
  • Added support for Windows 64-bit and SQL Server 2005 64-bit for x64 CPUs (MAJOR ENHANCEMENT)
  • Added BLOB support in recovery of deleted rows and rows in truncated and dropped tables when using database
  • sources for recovery (online database files and MDF files) (MAJOR ENHANCEMENT)
  • Significantly improved performance of data recovery from MDF files, online or detached (MAJOR ENHANCEMENT)
  • Added support for online transaction log and database files on drives mounted as NTFS folders.
  • Added support for in-row values for BLOB types.
  • Added SERVER_NAME column to Connection Monitor table allowing for filtering by the name of the server
  • where transaction log was created.
  • Added xp_ApexSqlConnectionMonitor_Enable and xp_ApexSqlConnectionMonitor_Disable extended procedures.
  • In generation of UNDO/REDO statements:
  • Added SET IDENTITY_INSERT ON/OFF for INSERT operations.
  • Added transaction wrapping for DELETE operations.
  • Changed preference for construction of WHERE statments to primary key over clustered index.
  • For heap tables, added generation of WHERE clause from values of all non-BLOB fields.
  • Added skipping of BLOB and TIMESTAMP fields.
  • In recovery from detached MDF files, added loading of meta-data from a live database when such is unaivalable in MDF files.
  • For recovery on SQL Server 2005, modified algorhitms to improve chances of success in suboptimal recovery scenarios.
  • Added SET NOCOUNT ON to recovery scripts.
  • Fixes:
  • A problem with conversion of _variant_t to __int64 (MAJOR FIX)
  • A problem with memory over-consumption (MAJOR FIX)
  • A problem with activation not taking immediate effect on the server side (MAJOR FIX)
  • A problem with old ID mapping feature (MAJOR FIX)
  • A problem with multiple value switches in CLI (MAJOR FIX)
  • Parsing of table names in command line interface (table names can now be specified with within angular brackets)
  • A problem with NULL values in WHERE statements.
  • A problem with UNICODE table names and table names with quotes in CLI and Recovery Wizard.
  • A problem with Connection Monitor with automatic restart.
  • A problem with Connection Monitor sometimes failing to flush rows from temporary login table.
  • A rare problem with table names on case-sensitive databases.
  • A problem with user ID showing as N/A even when it's known.
  • A problem with refreshing of transaction log operations grid.
  • A problem with NULL/NOT NULL flag in table DDL scripts.
  • A rare problem with transaction log reading.
  • A rare unhandled NULL exception.
  • A rare problem of mistaken table ID for dropped tables on SQL Server 2005.
  • An exception in About box when not connected to any server.
  • Several errors in captions and messages.
  • Several icons in the Log Filter dialog.
  • Changes:
  • Last used filter now is stored per server and database.
  • Added server name to login information captured by Connection Monitor.

New in ApexSQL Log 2005.02 (Sep 26, 2006)

  • new product