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

Overcoming Imposter Syndrome: A Plan

By

My most recent bout with imposter syndrome was with ISACA’s Digital Trust Ecosystem Framework...

Advice I Like: Celebrate Success

By

“On the way to a grand goal, celebrate the smallest victories as if each...

Programmatically Retrieving MLV Lineage and Refresh Times

By

Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...

Read the latest Blogs

Forums

BCA KCP Praya Telp:Cs.08216977726

By diawifi

Whatsapp:08216977726 Pertokoan Lion Mart, Jl. Jend. Sudirman, Praya, Kec. Praya, Kabupaten Lombok Tengah, Nusa...

BCA KCP Utan Kayu,Telpon/Wa 0821-8200-239

By ahsan

Jl. Utan Kayu Raya No.94, RT.12/RW.10, Utan Kayu Utara, Kec. Matraman, Kota Jakarta Timur,...

Visit the forum

Question of the Day

Increase Deadlock Detection

How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?

See possible answers