Bug with IgnoreConstraintNames and WITH NOCHECK constraints

JackAceJackAce Posts: 75 New member
edited April 24, 2014 10:38AM in SQL Compare Previous Versions
I am able to reliably reproduce an issue with the IgnoreConstraintNames option with SQL Compare

If you specify IgnoreConstraintNames and two constraints have different WITH NOCHECK attributes set, then SQL Compare will try to create the constraint without dropping it first.

I was able to reproduce this issue on a database created from scratch with just two tables in it. Here are some images that illustrate the issue:

I also have a backup of both databases if you have any problems reproducing this.


Sign In or Register to comment.