Code to find out the statement that caused the trigger to fire!

By Bill Graziano on 16 April 2002 | Tags: Triggers

Vyas submitted "This example trigger uses DBCC INPUTBUFFER to track the actual SQL statements that are modifying the data. Handy for tracking and auditing purposes."

Link: Code to find out the statement that caused the trigger to fire!

Using DDL Triggers in SQL Server 2005 to Capture Schema Changes (13 August 2007)

Audit Triggers for SQL Server (8 May 2002)

An Introduction to Triggers -- Part II (4 November 2001)

An Introduction to Triggers -- Part I (30 April 2001)

Replicating Triggers (14 August 2000)

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources

Code to find out the statement that caused the trigger to fire!

Related Articles

Other Recent Forum Posts

Subscribe to SQLTeam.com

Resources