Tracking down culprit that dropped a trigger in SQL 2000.

  • 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,

  • Multiple post, please post replies here.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply