This is a discussion on Track changes made to SQL Server within the SQL Server forums, part of the Microsoft SQL Server category; --> "Erland Sommarskog" <esquel@sommarskog.se> wrote in message news:Xns9A5EED43C918FYazorman@127.0.0.1... > John Sheppard (nospam@spamspam.com) writes: >> hmm, ok, I've found out about ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| "Erland Sommarskog" <esquel@sommarskog.se> wrote in message news:Xns9A5EED43C918FYazorman@127.0.0.1... > John Sheppard (nospam@spamspam.com) writes: >> hmm, ok, I've found out about DDL triggers. These are the go...much >> easier >> than profiler... > > True, you could set them up and siphon off everything into a table, > and you don't have to damn yourself for not running profiler. > > I don't remember on the top of my head if the XML returned by the > eventdata() function includes the statement that fired the trigger, > but if it does, it's a walk in the park. > > Still, keep in mind that you must have a reference database so that > you can test the script however you compose it! > > -- > Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se > > Books Online for SQL Server 2005 at > http://www.microsoft.com/technet/pro...ads/books.mspx > Books Online for SQL Server 2000 at > http://www.microsoft.com/sql/prodinf...ons/books.mspx They do...I just have to figure out which events to put on the trigger and I think its all good to go.. Thanks heaps for all your help man... Much appreciated John |
| Thread Tools | |
| Display Modes | |
|
|