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.

If you like this article you can sign up for our weekly newsletter. There's an opt-out link at the bottom of each newsletter so it's easy to unsubscribe at any time.

Email Address:

Related Articles

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)

Other Recent Forum Posts

Patch Installation Failed On SQLServer 2008 R2 SP2 (0 Replies)

fulltext stoplists (0 Replies)

array (0 Replies)

some help pls.... (6 Replies)

Control XML Output (0 Replies)

Create database (10 Replies)

Getting duplicate records, don't know why (4 Replies)

List all the tables from Stored Procedure (0 Replies)

Subscribe to SQLTeam.com

Weekly SQL Server newsletter with articles, forum posts, and blog posts via email. Subscribers receive our white paper with performance tips for developers.

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -