Tracking down culprit that dropped a trigger in SQL 2000

• vince.tran

  Old Hand

  Points: 347

  More actions

  July 8, 2009 at 4:06 pm

  #155931

  Hello Community,

  We had an issue with a trigger being dropped from a SQL 2000 production database server. Management is asking if there's a way to trace down the culprit. I've checked the SQL logs but there isn't anything listed. Does anyone have any suggestions going forward on how to set this up either via more granular logging or other means?

  What we want to do is to be able to track down activities as far as who was in the database and if there are any activities such as deleting stored procedures or triggers and have that captured. I know this might ramp up the logging activities but we suspect that there is some foul play involved and will need to turn it on (if possible).

  Any help would be greatly appreciated.

  Thanks,

• Lynn Pettis

  SSC Guru

  Points: 442467

  More actions

  July 8, 2009 at 4:11 pm

  #1022008

  Multiple post, please post replies here.