Bug with IgnoreConstraintNames and WITH NOCHECK constraints

JackAce

I am able to reliably reproduce an issue with the IgnoreConstraintNames option with SQL Compare 10.4.8.87.

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:
http://imgur.com/a/mfDmp


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

JackAce

FYI - As a work around, we have been specifying IgnoreWithNocheck, but this is not ideal.

Brian Donahue

I believe this is an issue that was fixed in 10.5, but then 10.5 has been removed temporarily while a bug regarding migration scripts is being investigated. If you do not use migration scripts, can you please try using SQL Compare 10.5 and see if that solves the problem?

http://downloads.red-gate.com/checkforu ... .0.611.exe

JackAce

We'll probably wait until 10.5 is available with all migration issues resolved. Is there an ETA on when it will be released again?

Brian Donahue

Work starts in November, so probably mid-December, all going well.

Brian Donahue

This issue should be fixed in version 10.7, which was released to Check for Updates yesterday.