July 2, 2009 at 7:23 pm
Hi.
We had a DML Trigger that was used to perform an insert to another table when something was inserted in the first table.
So the trigger was setup to fire on the ON INSERT of the first table.
This morning, we were alerted by a user that something that should be populated in table 2 wasn't, and found that the trigger on the first table has been disabled and is not firing.
I remember reading something about triggers dropping off tables under some circumstances, and am wondering of adding or changing a field in table 1 could have cause the trigger to disable itself.
Can anyone fill me in on any circumstances where a DML Trigger might drop off a table, and when you need to be mindful of this?
July 2, 2009 at 7:54 pm
Anyone with ALTER TABLE permissions for the table with the trigger on it could have executed a DISABLE TRIGGER statement. See the following link within BOL:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/tsqlref9/html/e6529f06-e442-437e-a7bf-41790bc092c5.htm
I couldn't find any evidence of articles within BOL that referred to a trigger being disabled by anything other than overt action by someone with at least ALTER permissions for the table, but then, I could have missed it easily. Hope that helps...
Steve
(aka smunson)
:-):-):-)
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply