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

ISACA AI Material/Exam Prep Discount (May 18 – June 30, 2026)

By

If you are considering any of the ISACA AI certs like the Advanced Artificial...

A Fabric solution can be very cost effective

By

Are you currently using Microsoft Fabric or considering migrating to it? If so, there...

Track SQL Server Configuration Changes Using the Error Log

By

Track SQL Server Configuration Changes Using the Error Log If you...

Read the latest Blogs

Forums

Before Using AI with Business Data, Read This

By rom_c99

Artificial intelligence tools are quickly becoming part of daily business operations, from document analysis...

Designing SQL Server ETL Pipelines That Don't Break at Scale

By SQL Expert

Comments posted to this topic are about the item Designing SQL Server ETL Pipelines...

Detecting Deadlocks Quickly

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Detecting Deadlocks Quickly

Visit the forum

Question of the Day

Detecting Deadlocks Quickly

In the Database Engine, when a deadlock is detected, what does the detection interval shrink to (in time)?

See possible answers