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,487 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,383 reads
One feature that I have been waiting for years! The new announcement around optimize...
Following on from my last post about Getting Started With KubeVirt & SQL Server,...
By DesertDBA
I haven’t posted in a while (well, not here at least since I’ve been...
I have change tracking configured in several databases, in QA and production environments, and...
is there a no code way to limit an ssis extract from excel to...
Hello Need help in pivoting this data set, the Pivot takes MIN/MAX on a...
In SQL Server 2025, what does this return?
CREATE TABLE Numbers ( n INT) GO INSERT dbo.Numbers ( n ) VALUES (1), (2), (3) GO SELECT PRODUCT(n) FROM dbo.NumbersSee possible answers