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,492 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
By Vinay Thakur
As discussed introduction of Always Encryption blog and initial Encryption at rest as TDE...
By Vinay Thakur
Transparent Data Encryption(TDE): TDE was initially introduced in SQL Server 2008 Enterprise Edition; this...
By Steve Jones
Only a little break for me. I’m actually heading to Las Vegas today for ...
Comments posted to this topic are about the item The day-to-day pressures of a...
Comments posted to this topic are about the item This Week's AI Trust Problem...
Comments posted to this topic are about the item Migrate SSRS Reports to PowerBI...
When thinking of the Identity property for auto incrementing columns and sequences for the same action, which can be used with the BIGINT data type?
See possible answers