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

By Bill Graziano on 16 April 2002 | 0 Comments | 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." Follow the link to Code to find out the statement that caused the trigger to fire!...

Discuss this article: 0 Comments so far. Print this Article. This page has been read 8,796 times.

If you like this article you can sign up for our newsletter. We send it out each week that we post a new article. There's an opt-out link at the bottom of each newsletter so it's easy to unsubscribe at any time.

Email Address:

Email This • Subscribe to this feed • Kick it • Save to del.icio.us • View blog reactions

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)