Using Triggers to Track Database Action History

By Bill Graziano on 18 September 2001 | Tags: Stored Procedures


Several State and Federal contracts that I have worked on in the past have wanted to keep track of all changes to a particular record, such as who modified the record, what kind of modification took place, and when the record modification occurred. I decided to solve this problem with triggers because I wanted to capture every action that occurred on a particular table.

Link: Using Triggers to Track Database Action History


Related Articles

Handling SQL Server Errors (5 April 2010)

Testing with Profiler Custom Events and Database Snapshots (22 June 2009)

Debugging Stored Procedures in Visual Studio 2005 (25 June 2007)

Writing CLR Stored Procedures in C# - Returning Data (Part 2) (23 June 2005)

Writing CLR Stored Procedures in C# - Introduction to C# (Part 1) (6 June 2005)

Managed Data Access Inside SQL Server with ADO.NET and SQLCLR (31 May 2005)

An Evaluation of Stored Procedures for the .NET Developer (22 March 2004)

Run CLR code from a stored procedure (14 October 2003)

Other Recent Forum Posts

How do you prevent duplicate transactions when importing overlapping CSV files? (2d)

Moving SQL Server to Fabric without rebuilding everything by hand ? (12d)

Moving SSIS packages to Fabric Lakehouse - best approach? (17d)

SSRS to Power BI Migration: How to handle multi-select params and subreports? (19d)

SQL Azure versions (24d)

Change drive path (86d)

Insert query not working (107d)

Finding Common Groups (124d)

- Advertisement -