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
By Steve Jones
I was looking back at my year and decided to see if SQL Prompt...
In the era of cloud-native applications, Kubernetes has become the default standard platform for...
By Steve Jones
I’ve often done some analysis of my year in different ways. Last year I...
Hi, below i show various results trying to reach our ftp site (a globalscape...
Comments posted to this topic are about the item Finding Motivation
Comments posted to this topic are about the item The Last Binary Value of...
What does this code return?
SELECT cast(0x2025 AS NVARCHAR(20))Image 1:
Image 2: 
Image 3: 
Image 4: 
See possible answers