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,494 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,386 reads
By SQLPals
SQL Server instance metadata inventory with PowerShell and SMO The purpose...
Disclosure: this post may contain links to books as an affiliate link. If you...
By Arun Sirpal
Every Claude conversation has a context window. It is the total amount of text...
Comments posted to this topic are about the item Celebrating 30 years of PostgreSQL,...
Hello, has anyone here ever provisioned and actually used an MS SQL Server with...
Comments posted to this topic are about the item No More Deadlocks
After detecting deadlocks in SQL Server 2025 and lowering the time threshold for detecting future issues, when does the Database Engine return to the 5s default interval?
See possible answers