SMO.script does not script a trigger state. Disabled triggers are not put back in a disabled state ! - by ALZDBA

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.


4
0
Sign in
to vote
ID 867404 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 5/5/2014 2:40:34 AM
Access Restriction Public

Description

SMO.script does not script a trigger state. Disabled triggers are not put back in a disabled state !
A table trigger that has been disabled, will become enabled and remain enabled when this script is being executed. 
This may cause failing DML when data is put into the table.

I tested this with SQL2008R2 an SQL2014
Sign in to post a comment.