Designing Tables for Audit Data in SQL Server

  • Article

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?


5,915 reads


Azure Storage tips


As a followup to my blog post Azure Data Lake Store Gen2 is GA,...

Managing Agent Jobs on Availability Group Servers


As always, the scripts in this post can also be found on our Git...

Permissions required for row counts to show up on Object Explorer Details


I ran into a rather obscure permissions problem the other day. Since I wasn’t...

Read the latest Blogs


Sql server Express 2017 and ssms

By kangarolf

Hi all, I've never used mssql express before but we had a small intranet...

Memory requirement

By Admingod

Looking for memory optimized tables. How would we know that the approx memory is...

Question on the use of schemas for access control

By chuck.forbes

I know that this is a long article, so, I totally understand if there...

Visit the forum


SQL Server Q&A from the SQLServerCentral community

Get answers