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

T-SQL Tuesday #202 Invitation: That One SQL Server Outage You’ll Never Forget

By

I am excited to host T-SQL Tuesday for the first time. I want to...

A Daily Report from Claude

By

Redgate had some Claude training recently, which I went through as my knowledge has...

A New Word: Gnossienne

By

gnossienne– n. the awareness that someone you’ve known for years still has a private...

Read the latest Blogs

Forums

Measuring Productivity

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Measuring Productivity

Importing Excel files into SQL Server using DuckDB and Python

By Cláudio Tereso

Comments posted to this topic are about the item Importing Excel files into SQL...

Tracking All the Queries

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Tracking All the Queries

Visit the forum

Question of the Day

Tracking All the Queries

I have 3 instances of a brand new long running query that are executing on a SQL Server 2025 instance. Query store is enabled. One of the queries is killed by the administrator, one is cancelled by the user. The other runs to completion. How many rows are in Query Store for this query?

See possible answers