Bug with compare script when trying to sync constraint names (v11.3.0.7)
I have table A with named default constraints and a named PK, table B is identical except the defaults and PK do not have a name.
When I run the deployment script to make table B the same as table A it does not handle the primary key and generates an error:
Msg 1779, Level 16, State 0, Line 1
Table 'tableA' already has a primary key defined on it.
I also note there is a link at the top of the screen to report bug, however when I click it (http://www.red-gate.com/messageboard/viewforum.php?f=154) I get the message "The forum you selected does not exist.".
Marvellous :-/

This bug is fixed in SQL Compare version 11.3.8
— Mike Upton, Project Manager