Auditing Primary key violation

Giganews Newsgroups
Subject: Auditing Primary key violation
Posted by:  vinu (vinu.t.19…@gmail.com)
Date: Thu, 6 Nov 2008

Hello experts

Is there a way to audit primary key violation error so that it tell me
application, user, server which caused it. Is it possible to do it through
profiler trace? if so, I want it to capture only when that error occurs
I tried the profiler trace by specifying the 2627  error code in the filter,
it still display all the statement that server is currently executing

System details
SQL Server 2000
Win 2003 Std

man
vinu

Replies