In June 2016 Microsoft released SQL Server 2016 but due to a bug in their Exchange 2016 release, we wanted to make sure that we performed very extensive testing of this latest version of SQL Server and its new auditing features to make sure we didn’t discover any bugs there too. We also performed very stringent testing of LOGbinder for SQL Server to make sure that our software continues to meet and exceed our internal standards.With the release of SQL Server 2016 came not only many new features but also some new audit events. These include audit events related to committing and rollback of transactions, handling master keys, column encryption keys, database scoped credentials, as well as events related to external data sources (think, for example, Hadoop), external file formats and external resource pools.
LOGbinder for SQL Server 3.0 includes the ability to handle these new events as well as many other improvements. Here are some of the highlights:
- Support for SQL Server 2016
- New installer – Our new installer automates some of the prerequisites required during the installation process. Installation time is now just a couple of minutes.
- Improved service resilience – We have improved on the delay that was reported by some customer when restarting/starting/stopping the service.
- Purge processed files - We have added a new option to purge SQL audit files that are no longer being used by SQL Server and have already been processed by LOGbinder.
- Enhanced application activity events - Information events written to the Windows Application log now include statistics including entries exported, elapsed processing time and events per second (EPS).
These are just a few of the improvements in this release of LOGbinder for SQL Server. For full details, check the release notes below.
Customers with current support and maintenance contracts can access the latest version at the link below. To upgrade to the latest version just run the installer on top of the previous version. No data or settings will be lost. Please note you will need to request a new license key for this version. You can do so by clicking on File in the LOGbinder Control Panel, then License and send the license information to licensing@logbinder.com.
Related information
Thank you for your hard work in protecting sensitive information, and thank you for your support!