Database Audit Specifications in SQL Server 2008
This is the final article of a three part series on Auditing in SQL Server 2008. This article shows how to setup a Database Audit Specification.
2008-09-30
2,246 reads
Auditing
2013-04-02 (first published: 2008-09-11)
15,381 reads
SqlCredit – Part 17: Exploring SQL 2005’s OUTPUT Clause
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.
2008-08-04
3,369 reads
SQL Server Audit in SQL Server 2008 – Part 2
Learn how to monitor database-level actions and write audit results to files.
2008-07-22
2,557 reads
Automate Audit Requests
In this article TJay Belt describes a process to help respond to audit requests in a timely manner
2008-06-18
2,393 reads
SQL Server Audit in SQL Server 2008 – Part 1
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.
2008-06-16
2,860 reads
Audit Database Changes in the Real World
Tjay Belt brings us a story of how auditing was actually implemented and a discussion of why particular decisions were made.
2008-06-11
9,081 reads
Audit Trails and Logging Part II
Continuing with Part II of his auditing series, Gsquared takes a look at active auditing techniques for your SQL Server.
2008-06-10
10,442 reads
Audit Trails and Logging Part I
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.
2008-06-09
14,303 reads
Using DDL triggers to audit events
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.
2008-05-15
3,467 reads
Blogs
Don’t Miss Out – SQL Server 2025 Unleashed Training Starts Next Monday!
Next Monday, Marchg 9, 2026, my one-day live online training SQL Server 2025 Unleashed:...
What is ALM in Fabric?
By HeyMo0sh
As someone who’s worked with data for over 20 years and with many cloud...
The Most Successful Startups in 2025 — And What They Have in Common
By HeyMo0sh
2025 belongs to the AI startups. If you peek into the tech headlines, you’ll...
Forums
A Quick Restore
Comments posted to this topic are about the item A Quick Restore
Guarding Against SQL Injection at the Database Layer (SQL Server)
Comments posted to this topic are about the item Guarding Against SQL Injection at...
Ola Hallengren Index Optimize Maintenance can we have data compression = page
I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...
Question of the Day
A Quick Restore
While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:
USE DNRTest BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO /* Bunch of stuff tested here */RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance. See possible answers