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

Setting FK Constraints in Data Modeler

By

One of the things a customer asked recently about Redgate Data Modeler was how...

Webinar: Navigating the Database Landscape in 2026

By

For a number of years, we’ve produced the State of the Database Landscape report,...

Claude AI Convinced Me Not to Build an iPad App

By

I coach volleyball and I do a lot of stat stuff on paper. I...

Read the latest Blogs

Forums

SSMS 22 Latest Update Crashing

By Phil Parkin

Hi all, I've just had to roll back my SSMS 22 version from 22.3.0,...

Transactional Replication setup issue

By DrAzure

Hi! I've been banging my head against the wall for 2 days now trying...

The Power of Data and Privacy

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Power of Data and...

Visit the forum

Question of the Day

What's the Date?

In SQL Server 2025, there is a new function that returns the current date without the time. What is it?

See possible answers