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

Exploring DiskANN: Part I: Understanding the Algorithm before the disk

By

How I used AI for this postChatGPT to generate images based on info specifically...

Learning Tool – Deepstash

By

A few months ago I started using Deepstash. Deepstash breaks books into the key...

New article – migrating from a named instance

By

Do you have a case where you have a named instance you'd like to...

Read the latest Blogs

Forums

Understanding Temp Tables and Table Variables in SQL Server

By sabyda

Comments posted to this topic are about the item Understanding Temp Tables and Table...

The Data API Builder MCP Server Tools

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Data API Builder MCP...

Collecting Data Is Hard

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Collecting Data Is Hard

Visit the forum

Question of the Day

The Data API Builder MCP Server Tools

The Data API Builder MCP Server, v2.x, includes a number of tools. What actions can these tools perform in your database?

See possible answers