SSDT Schema Compare script doesn't re-enable DDL Triggers - by Andrew Miller - WI

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 812134 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 12/20/2013 1:42:09 PM
Access Restriction Public


Our SSDT project doesn't contain any database triggers.  Our target database contains a single database trigger, that is managed by our DBA group, so we don't want to delete it.  When we generate a script through Publishing the project, the trigger is disabled and re-enabled like expected.  However, when we generate a script through Schema Compare, the "DISABLE TRIGGER ALL ON DATABASE" is in the script, but the trigger is never re-enabled.  In both instances, the "Disable and reenable DDL triggers" option is checked.  

Using SSDT Oct 2013.
Sign in to post a comment.
Posted by Microsoft on 12/23/2013 at 10:07 AM
Hi Andrew,

Thanks for reporting this issue in the scripting behavior from Schema Compare.

We will triage this issue on our end and will update you on the outcome.

Thanks & Regards,