ALTER TRIGGER implicitly enables a disabled trigger - by

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 781722 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 3/19/2013 8:44:13 PM
Access Restriction Public


From observation, running ALTER TRIGGER on a disabled trigger will enable it.

I consider it incorrect behaviour, but please keep in mind that if it is intended behaviour that:

* ALTER TRIGGER's documentation says that it "Modifies the definition of a ... trigger".
* The documentation does not explicitly state what the "definition" consists of.
* The documentation does not explicitly state that ALTER TRIGGER will enable a disabled trigger.
Sign in to post a comment.
Posted by samot-dwarf on 11/12/2015 at 8:23 AM
Under SQL 2014 the behavior is changed again. Triggers remains now disabled after altering them.
Posted by Tom.Thomson on 9/10/2013 at 4:59 AM
I wonder how long "a couple of weeks" is going to be. Twelve weeks already feels like rather more than "a couple".
Posted by Microsoft on 6/19/2013 at 1:43 PM
Added to the remarks, that changing the trigger using ALTER TRIGGER enables the trigger. It will take a couple weeks for the change to appear online. Thank you for reporting this.
Posted by EdSF1 on 6/6/2013 at 1:00 PM
Please do add to documentation - I'm another one of those "huh"? folk:

Thank you.
Posted by Microsoft on 5/3/2013 at 12:05 PM
The behavior you are seeing is by design. We will document it in Books Online. Thanks for reporting this.

Umachandar, SQL Programmability Team