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

Reading SQL Server File Headers with DBCC FILEHEADER

By

I’ve been doing a deep dive into SQL Server on-disk structures lately, and one...

T-SQL Tuesday #197 – An impactful session or two from a conference – RECAP

By

Thanks to everyone who joined the blog party this month. I noticed three themes...

OpenClaw- Agentic Engineering

By

This week has training on AI – Cyber security experts – Omar Santos and...

Read the latest Blogs

Forums

What's new in R 4.6

By Steve Jones - SSC Editor

Comments posted to this topic are about the item What's new in R 4.6

Interesting Changes in R

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Interesting Changes in R, which...

PostgreSQL String Functions Part 1

By Shivayan Mukherjee

Comments posted to this topic are about the item PostgreSQL String Functions Part 1

Visit the forum

Question of the Day

Identities and Sequences V

When thinking about the identity property and sequence objects, which of these can generate values before an insert statement is executed?

See possible answers