Incorrect constraint syncing in SqlCompare 8.50.12.20

CarissaMiller

I ran Sql Compare 8.50.12.20 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?

Thanks,
Carissa

peter.peart

Thanks for your post. I believe there has been some work done here, but the best thing really is for you to try out V10 in your environment.

Is this something you're able to do? If it isn't fixed, we can then raise an issue for V10.

Pete