Articles

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?

2008-04-15

5,915 reads

Blogs

Finding Balance: Things Will Come Up

By

I have a presentation on finding balance in your career that got quite a...

Who Are You Doing It For?

By

But as I've matured over the years, I came to realize that I needed...

Presenting Twice in May 2026

By

I will be presenting my latest session, Documenting Your Work for Worry-Free Vacations, in-person...

Read the latest Blogs

Forums

How to change the FDLaunch Error log file location

By schleep

The file FDLAUNCHERRORLOG gets created in the default <instance>\MSSQL\Log folder. So far, I've found...

what data type i should use for roversion col and can i use less than greater

By rajemessage 14195

can i use Rowversioncol ( in my database it's synonyme timestamp is used) to...

Radius Latitude Longitude

By HeftSteady

I have a table with latitude longitude in the format.  45.123456 , -111.123456 ,...

Visit the forum

Question of the Day

A Fun Computer Quote

Which movie featured this quote?

"All programs have a desire to be useful."
Happy April Fools!

See possible answers