Incorrect constraint syncing in SqlCompare 184.108.40.206
I ran Sql Compare 220.127.116.11 to compare two Sql Server databases, and there was a check constraint on the source table in the form ((a and b and c) or (d and e and f)). However, Sql Compare read it as ((a and b and c or d and e and f)) and inserted this version in the synchronization script, which changes the logical meaning of the constraint. Has this been fixed in future versions of Sql Compare?
0 · Share on Twitter