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,476 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,377 reads
By Brian Kelley
Core skills depends on the position, but the point is that ensuring you have...
By Steve Jones
zverism – n. the wish that people could suspend their civility and indulge in...
By Kevin3NF
The Source Control Dilemma Every DBA has been there. Trying to keep track of...
Comments posted to this topic are about the item Is GenAI Coming Faster Than...
Comments posted to this topic are about the item Local Storage Options
Comments posted to this topic are about the item DeepSeek: What is new with...
I'm setting up a SQL Server 2019 instance and we are planning on using SMB storage for our database files. However, the file share isn't ready, so the idea is to use the \127.0.0.1dbfile as the location to start and then move these files to the remote server. Can I do this?
See possible answers