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?
2008-04-15
5,915 reads
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.
2008-02-29
7,485 reads
SQL Auditing - Generate a listing of the SQL logins, and the permissions for each database on a server.
Update to Simon Facer's script.
2011-05-23 (first published: 2007-09-25)
13,382 reads
By Brian Kelley
Tech conferences aren't just for networking and learning how to address a problem you're...
By DataOnWheels
When I created the website on WordPress, I was expecting all the features I...
By Steve Jones
I wrote a piece on the new SUBSTRING in SQL Server 2025 and got...
Comments posted to this topic are about the item Getting the Schema for Tables
Comments posted to this topic are about the item An Unexciting Exciting Release
Comments posted to this topic are about the item UNLOGGED Tables in PostgreSQL: When...
What happens when I run this on SQL Server 2022 in the AdventureWorks2022 database?
SELECT OBJECT_DEFINITION (OBJECT_ID(N'Person.Person')) AS [Object Definition]; GOSee possible answers