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

Experimenting with CHOOSE: #SQLNewBlogger

By

I was looking over the CHOOSE() function while editing an article at SQL Server...

Fighting Procrastination?

By

Here is another short video (~ 15 minutes). This is by the author of...

A Fun Prize at the PASS Data Community Summit

By

I had a briefing for the 2026 PASS Data Community Summit, which is just...

Read the latest Blogs

Forums

Alamat Telp BCA KCP Cirendeu +62 838-4945-0961

By Halo_BCA

Wa:083849450961 Jl. Raya Cirendeu No.14, Cireundeu, Kec. Ciputat Tim., Kota Tangerang Selatan, DKI Jakarta...

Alamat BCA KCP Altira Sunter Telp 0821 6277 387

By Layanan BCA 24 JAM

Altira Bussiness Park, Jl. Yos Sudarso Kav 85 Blok B No.1-2, RT.9/RW.11, Sunter Jaya,...

SQL Server 2025 Server-level Roles

By Steve Jones - SSC Editor

Comments posted to this topic are about the item SQL Server 2025 Server-level Roles

Visit the forum

Question of the Day

SQL Server 2025 Server-level Roles

In SQL Server 2022+, what does the ##MS_DatabaseConnector## role allow?

See possible answers