SQL Server 2005 introduces the OUTPUT clause, a bit of magic that allows us to get the identity value, plus a number of other values, from an INSERT, UPDATE, or DELETE, which all have different interaction with OUTPUT. This article concentrates on INSERT.  Read more...

Learn how to monitor database-level actions and write audit results to files.  Read more...

In this article TJay Belt describes a process to help respond to audit requests in a timely manner  Read more...

SQL Server 2008 February CTP introduces a new feature, SQL Server Audit. This feature facilitates auditing of Database Engine events by providing simple T-SQL statements to enable, store, and view audits on server and database objects. Part 1 of this series focuses on the server level events.  Read more...

Tjay Belt brings us a story of how auditing was actually implemented and a discussion of why particular decisions were made.  Read more...

Continuing with Part II of his auditing series, Gsquared takes a look at active auditing techniques for your SQL Server.  Read more...

Auditing becomes more important every day as new requirements for data access are implemented. New author Gsquared, well known in the forums, brings us a look at types of audits and some details on passive auditing techniques.  Read more...

Learn how using the OUTPUT clause in SQL Server 2005 queries simplifies T-SQL code and returns results of rows changed by an INSERT, UPDATE or DELETE SQL command.  Read more...

Create DDL table in SQL Server 2005 to audit Data Definition Language (DDL) trigger events when DML statements run. Define DDL trigger to track SQL changes.  Read more...

My company is just starting to look at adding functionality to retain historical data for key tables and columns for auditing purposes in many of our SQL Server databases. I have seen some of your recent tips related to triggers (Forcing Trigger Firing Order in SQL Server and Trigger Alternatives in SQL Server - OUTPUT Clause). Based on using triggers or a similar technology, what is the best way to store the historical data?  Read more...

Auditing activities on your database servers becomes more important all the time. But ensuring that schema changes do not occur without your knowledge may be more important for a stable system. James Greaves brings us a great technique using DDL triggers for doing this.  Read more...

Part 2 of this article illustrates how to enable Change Data Capture on a database, on a table and how SQL Server tracks the data changes of the CDC enabled table.  Read more...

Part one of this series illustrates how to enable Change Data Capture on a database, and on a table, and how to keep track of Data Definition Language changes on a table.  Read more...

Longtime SQL Server guru David Poole brings us a look at one of the thorny problems a DBA faces: tracking down illicit users.  Read more...

In a new DBA role, Daryl Quadros brings us a list of the first tasks you should perform.  Read more...

As part of your performance audit, you will need to examine each database located on each of your SQL Server instances and examine some basic database settings.  Read more...

Tjay Belt brings us a story of how auditing was actually implemented and a discussion of why particular decisions were made.  Read more...

Longtime SQL Server guru David Poole brings us a look at one of the thorny problems a DBA faces: tracking down illicit users.  Read more...

Continuing with Part II of his auditing series, Gsquared takes a look at active auditing techniques for your SQL Server.  Read more...