External Article

Designing Tables for Audit Data in SQL Server

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?

Blogs

Elastic Jobs for Azure SQL DB

By

I know if you are a SQL Server DBA using Azure SQL DB, you’ve...

Undercover Catalogue 0.4.4 Released – Database Last Accessed Time and NEW Snapshot Module

By

Full documentation on the Undercover Catalogue can be found HERE It’s been a while...

Familiar Sights

By

Yesterday was a long day in London. I arrived late in the am, and...

Read the latest Blogs

Forums

Full vs. Incremental Loads – Data Engineering with Fabric

By John Miner

Comments posted to this topic are about the item Full vs. Incremental Loads –...

Restoring the Resource Database

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Restoring the Resource Database

Missing the Office

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Missing the Office

Visit the forum

Question of the Day

Restoring the Resource Database

How can I restore a version of the Resource Database in SQL Server 2022?

See possible answers