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

Methodology for dealing with bad data in production

By

Pinal Dave wrote up his methodology for what to do when you discover bad...

How to Provision an Azure SQL Database

By

Aside from spinning up a SQL Server instance container, the free Azure SQL Database...

Claude finds two cryptographic weaknesses (but the sky isn’t falling)

By

If you haven't seen the announcement, Anthropic was able to utilize Claude (Mythos Preview)...

Read the latest Blogs

Forums

Kontak BCA KCP Semanggi Telp:08218154392

By Layanan_BCA_24jam

WA CS (08218154392) Wisma GKBI, Jl. Jenderal Sudirman No.28 Suite G 01, RT.14/RW.1, Bend....

Why SQL Server Database Attach fails and how to repair it

By Nisarg Upadhyay

Comments posted to this topic are about the item Why SQL Server Database Attach...

Fixing P1 Queries

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Fixing P1 Queries

Visit the forum

Question of the Day

BIT_COUNT() IV

In SQL Server 2025, I run this code:

select bit_count('A')
What is returned?

See possible answers