The new release of ApexSQL Log, an auditing and recovery tool for SQL Server databases is announced for Q3 2013. As we are closing to the release, we would like to inform you about improvements and changes we have implemented
The server side components (SSC) are no longer required for a local SQL Server instance auditing
Previous ApexSQL Log versions required installation of server side components (several DLL files added to the Binn folder of the SQL Server instance, and stored procedures created in the master database) whether the SQL Server instance was a local or a remote one. As the SSC installation was not always permitted by internal regulations, we have changed the server side components requirement – it’s no longer required for a local SQL Server instance auditing
Faster and easier SSC installation for remote servers
Server side components are not installed by default or as a part of regular installation as they are not needed for local servers. To audit remote SQL Server instance, server side components must be installed locally on the remote machine, using the Manage server-side components on a local servers option
While installing SSC, the setup prompts the user to select a SQL Server instance and automatically tries to connect using Windows authentication. If it fails, the manual logon settings prompt is shown
Additionally, the Manage server-side components on a local servers option provides information of already installed SSC’s on local SQL Server instances, with the possibility to uninstall desired SSC
Optimized session wizard with simplified data sources selection
The project management feature, used in previous version of ApexSQL Log, is removed. Instead, the new version introduces the Session, a kind of step-by-step project dialog. When started, ApexSQL Log opens a new session dialog asking for a database selection and user authentication
The next step is the selection of data sources to be read and analyzed. This step is an improvement as the user can select both detached or transaction log backups, and database backups using a single dialog
Redesigned time range filter with new options
The next session step shows redesigned the Time range filter, along with other filters available via appropriate tab options. We have implemented two new time filter options
- The Last [value] hours in data sources, and
- The First [value] hours in data sources
Also, instead of the Whole transaction log, the Last 24 hours in data sources option is set as the default one
Improved performance
ApexSQL Log 2013 provides up to 12x faster auditing via GUI, and up to 5x faster result grid filtering on large transaction logs (with over one million operations). Here is the summary of 2011 vs. 2013 version comparison tests:
- Transaction log with 250K operations: 15.15 min vs. 1.45 min – 7x faster
- 500K operations: 42 min vs. 3.45 min – 10x faster
- 1M operations: 150 min vs. 11 min – 12x faster
Discontinued Connection monitor feature
Due to inaccuracy (within 3ms due to SQL Server design) and overlapped functionality (auditing connection specific information, such as a client host and an application used to perform the transaction) with ApexSQL Audit and ApexSQL Trigger, the Connection monitor feature is removed from ApexSQL Log 2013
September 4, 2013
