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

Monday Monitor Tips: Intelligent Alert Thresholds

By

At the recent Redgate Summit in Chicago, I demo’d (lightly) the ML based Alert...

A New Word: los vidados

By

los vidados – n. the half-remembered acquaintances you knew years ago, who you might...

In-Person CISA Training – April 13-16, 2026

By

I will be leading an in-person Certified Information Systems Auditor (CISA) exam prep class...

Read the latest Blogs

Forums

String_agg not working as needed

By DaveBriCam

I'm trying to get this string_agg to put all the 'comments' into one result...

Vectors in SQL Server 2025

By Daniel Calbimonte

Comments posted to this topic are about the item Vectors in SQL Server 2025

Odd Sequences

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Odd Sequences

Visit the forum

Question of the Day

Odd Sequences

What values are returned from this code?

CREATE SEQUENCE NumericSequence
    AS NUMERIC(5,1)
    START WITH 1.0
    INCREMENT BY 0.1;
GO
SELECT NEXT VALUE FOR NumericSequence
GO
SELECT NEXT VALUE FOR NumericSequence
GO

See possible answers