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

PlanTrace Now Supports PostgreSQL

By

PlanTrace Now Supports PostgreSQL The same plan analysis you know from...

A New Word: the Kinder Surprise

By

the kinder surprise – . the point in your early adolescence when you realize...

Crash-Consistent Snapshot Cloning - Hyper-V Edition

By

If you’ve been following my T-SQL Snapshot Backup series, most of what I’ve covered...

Read the latest Blogs

Forums

The New Wave of Security Threats

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The New Wave of Security...

There's Too Much to Learn

By Steve Jones - SSC Editor

Comments posted to this topic are about the item There's Too Much to Learn

How to Calculate Distance Between Coordinates in SQL Server

By Imran2629

Comments posted to this topic are about the item How to Calculate Distance Between...

Visit the forum

Question of the Day

SSoL Support on the OS

On which Linux versions is SQL Server 2025 on Linux supported?

See possible answers