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,493 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,385 reads
I’ve been doing a deep dive into SQL Server on-disk structures lately, and one...
By DataOnWheels
Thanks to everyone who joined the blog party this month. I noticed three themes...
By Vinay Thakur
This week has training on AI – Cyber security experts – Omar Santos and...
Comments posted to this topic are about the item What's new in R 4.6
Comments posted to this topic are about the item Interesting Changes in R, which...
Comments posted to this topic are about the item PostgreSQL String Functions Part 1
When thinking about the identity property and sequence objects, which of these can generate values before an insert statement is executed?
See possible answers