Friday, June 05, 2009

Default trace - A Beginner's Guide - SQLServerCentral

 

We have all been subject to or know someone who has been in a situation where an object has been altered/created/deleted, without our knowledge, and the application comes to a screeching halt. After fixing the problem, your boss asks you some questions, like what happened, why did it happen, and who did it. SQL Server 2005 introduced a new type of trigger called a DDL trigger that can provide all the answers we need; however, you did not get a chance to implement this functionality. So... what do you do?

Default trace - A Beginner's Guide - SQLServerCentral

No comments: