I’m working with a SQL Server 2008 installation that was maintained for years by another team of programmers.
I’m having a problem that rows of data seem to be mysteriously disappearing from a specific table in my server.
I would like to be able to set up some sort of monitoring system that would tell me when the table is modified, and a summary of the modification.
I think that “triggers” might be what I’m looking for, but I’ve never used them before. Are triggers what I want to use, and if so, what is a good resource for learning to use them? Is there a better solution?
I think that I should mention that the table I’m referring to is not that frequently updated, so I don’t think that adding a little bit of overhead should be a big deal, but I would prefer a solution that I can brush away once the problem is resolved.
I think you have it figured out. A trigger is likely your best bet as it’s as close to the data as you can get. Inspecting the code (programming or even a stored procedure) would not give you as much an assurance as a trigger would; a Delete trigger in this case.
Check out this article: http://www.go4expert.com/forums/showthread.php?t=15510