Subscribe to our bi-weekly newsletter





Reading the SQL Server Transaction Log

Reading the transaction log offers the ability to audit and investigate database activity after the fact. The format in which the SQL Server transaction log is written requires careful decoding of each item to understand which values have been affected. There has always been some debate as to whether or not there are real benefits to be gained from accessing the information in the transaction log. This white paper will endeavor to answer that question

Creating a successful auditing strategy for your SQL Server databases

The purpose of security auditing is to identify all attacks, unlawful or malicious activities which might be taking place on your server. Keeping track of who has access rights, who has attempted access, and what has been done by people with access rights has become a crucial activity in identifying and pinpointing vulnerabilities in your security strategy

This whitepaper provides some guidelines as to how you can create a suitable auditing strategy for your environment and which SQL Server features may be useful to you in your quest for the perfect auditing strategy

Understanding the SQL Server audit

In this whitepaper we will show how auditing was done in SQL Server prior to 2008 and onwards. We will explain the auditing components, reading the audit file data, securing the audit logs, restarting the SQL Server after a forced shutdown, and point out the auditing best practices...