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

Don’t Fear the Technology

By

The concern that a particular technology is going to destroy the world seems to...

Creating a Custom SQL Server Security Checklist Using the DoD STIG

By

The STIG is detailed, which is a good thing, but I found myself wanting...

Creating a Local Model Chatbot on Windows

By

After my session at VSLive last week, I had a few questions from the...

Read the latest Blogs

Forums

RegEx Functions III

By Steve Jones - SSC Editor

Comments posted to this topic are about the item RegEx Functions III

Optimized Locking in SQL Server 2025: Fewer Locks, Less Blocking, and the Cases It Cannot Fix

By vgupta

Comments posted to this topic are about the item Optimized Locking in SQL Server...

Finely Tuned Models

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Finely Tuned Models

Visit the forum

Question of the Day

RegEx Functions III

If I run the REGEXP_LIKE() function, does it match values in a case-sensitive fashion, or a case-insensitive fashion by default.

See possible answers