Raleigh – December 16, 2011 – ApexSQL, a Microsoft Gold Certified Partner and leading provider of Microsoft SQL Server solutions, today announced the release of ApexSQL Log 2011. The new version features full SQL Server Denali support and includes outstanding performance and scalability improvements as well as many other new features
ApexSQL Log 2011 includes the following new features and improvements:
- Improved performance – up to 40% faster auditing
- A new 64-bit architecture
- Improved stability and memory management when auditing transaction logs larger than 2 GB
- Support for SQL Server Denali
Other new features:
- Support for SQL Denali DDL operations:
- CREATE/ALTER/DROP SEQUENCE
- CREATE/ALTER/DROP TABLE AS FILETABLE
- CREATE/DROP COLUMNSTORE INDEX
- Auditing, replaying or reverting changes:
- affecting compressed and SPARSE columns
- affecting vardecimal objects
- made by SELECT INTO statements
- Improved usability of key dialogs
“With ApexSQL Log 2011 there is virtually no limit to the physical size of the transaction logs you want to audit, and it does it considerably faster too”
Brian Lockwood
President
“…as an insurance policy against accidental SQL data deletion, etc … I am very pleased to say that the ApexSQL Log Tool has exceeded our expectations and I now consider it a necessity when working with SQL databases”
Craig Hatley
Director of Operations
Iatric Systems, Inc.
For more information visit the ApexSQL Log product home
About ApexSQL
ApexSQL is a leading vendor of tools for Microsoft SQL Server. ApexSQL products help SQL Server developers and DBAs accomplish complex tasks quickly, easily and accurately, including database auditing, recovery, change management, development, documentation and more. Headquartered in Raleigh, North Carolina, ApexSQL is a Microsoft Gold Certified Partner and has over 8,000 customers in over 120 countries worldwide.
About ApexSQL Log
ApexSQL Log is a SQL Server Transaction Log reader that allows viewing transaction log data in read-friendly format. Audit and undo SQL database changes of your choosing. Determine who changed the data and when the change occurred. Read the transaction log to find out who created, changed or dropped a database object
December 16, 2011