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?

External Article

Analyze and Correct a large SQL Server MSDB Database

It has come to my attention that some of our MSDB databases are getting what I would consider large for a system database. Some of our MSDB databases are over 2 GB which is a little perplexing because I know we do not create any user defined objects in that database. Can you give me some insight into the issue? I know we have this issue with both SQL Server 2000 and 2005 instances.

Blogs

Vibe Coding a Login Tracking System

By

A customer was asking about tracking logins and logouts in Redgate Monitor. We don’t...

4 CPE Opportunity (Virtual) for Charity

By

Every year, the South Carolina State Internal Auditors Association and the South Carolina Midlands...

Data Céilí 2026 Call for Speakers!

By

Data Céilí 2026 Call for Speakers is now live! Data Céilí (pronounced kay-lee), is...

Read the latest Blogs

Forums

Intermittent Service Freezes and "State 23" Authentication Failure

By avatar123

Environment: SQL Server: 2019 Enterprise (15.0.4430.1) OS: Windows Server 2022 Standard (Build 20348) Virtualization:...

SQL Server audit with windows ad group

By pollando

I am trying to create a filter on a SQL Server audit to capture...

Deadlock graph anomaly

By Databae

I've come across what appears to be a strange deadlock anomaly. As seen in...

Visit the forum

Question of the Day

Deprecated Feature Tracking

From T-SQL, without requiring an XEvent session, can I tell which deprecated features are being used on my instance?

See possible answers