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

On Speaking Well

By

Professor Patrick Winston of MIT used to give a one-hour talk about how to...

Monday Monitor Tips: Oracle Custom Metrics

By

One of the popular features of Redgate Monitor has been the ability to add...

Walking Through a Planned Failover: SQL Server Always On Availability Groups on Kubernetes

By

When building the sql-on-k8s-operator, I wanted to make sure it could handle both planned...

Read the latest Blogs

Forums

Troubleshooting WQL in custom PBM conditions?

By mastershake

Hi, I'm currently trying to implement policy based mgmt with a condition to query...

Analysis of Locking Issues on Secondary Replicas in AlwaysOn Availability Groups

By abdalah.mehdoini

We have an AlwaysOn architecture with four replicas: two running in synchronous commit mode...

The Vector Data Type

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Vector Data Type

Visit the forum

Question of the Day

The Vector Data Type

What is the vector data type in SQL Server?

See possible answers