calculated Comparision failed primary Key not found, but exists
There is an PK defined as PRIMARY KEY CLUSTERED, this Key will not be found AS comparison Key in Version 12, in Version 11 OK
Unfortunately we’re not able to reproduce this issue in our lab. If the primary keys have different names on left/right then both versions 11 and 12 report “unable to compare” but we can’t find any regression in the new major version. We will be happy to continue the investigation if you can send us a reproduction.
-
Sam Blackburn commented
Could you send some details to support@red-gate.com? It would be useful for us to have more info regarding this bug.
I've had a go at reproducing the issue and have noticed that Compare won't automatically select a primary key as the comparison key if the primary key has a different name in the source versus the target database. This seems to be the case for both 11.6 and 12.0. You can however select the comparison key by hand.
Kind regards,
Sam Blackburn
Software Developer, SQL Compare Team