Comments
1 comment
-
Hi there,
This sounds like the SQL Differences pane matching has gone a bit wrong, if you can post an example or screen shot I will take a look at it.
We actually consider WITH NOCHECK a semantic difference and there is an Ignore WITH NOCHECK option on the Project Configuration > Options > More Options dialog to disable this behaviour.
Thanks,
Jonathan
Add comment
Please sign in to leave a comment.
This occurs when the table being compared has two check constraints.
The two check constraints on the source and target tables are the same with the exception that one of the constraints on the target table was defined with nocheck option.
SQL Compare 6 Beta detects this difference and reports that the constraint is missing from the target table.
The other constraint is reported correctly as identical.