Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
BogeyGrinder
Starting Member
6 Posts |
 Posted - 2011-12-05 : 14:37:01
|
| I'm having a issue in my database with some triggers becoming disabled (triggers on tables - not database triggers).I am not having any luck narrowing down how/when/why this is happening. It does not seem to coincide with errors from my application or anything of the sort.I've attempted a DDL trigger on the "ALTER_TABLE" event to capture any instance of a command such as "ALTER TABLE XXX DISABLE TRIGGER ALL". I haven't captured anything.Anyone have any tips on how I can audit a single "disable trigger" command or other ideas? This isn't occurring often (once a week) and the application is an OLTP system, so I'm a little afraid of running SQL Profiler for a period that long and filtering for any occurrences of altering triggers. |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2011-12-05 : 16:27:36
|
| Have you looked in the default trace? I'm not sure if it's logged, but worth a test.--Gail ShawSQL Server MVP |
 |
|
|
|
|
|
Tracking when/how triggers are disabled