What are the challenges you face when working across database platforms? Take the survey
Options

Not matching columns with same name and type..

After compare, SC wants to create a new column for one that should match and rename a column of a different name. After compare, it looks something like this:

.
.
.
[FirmId] [int] NOT NULL,                                                  ->
[IsPrivate] [bit] NOT NULL CONSTRAINT [DF_IsPrivate] DEFAULT ((0)),       ->
[MethodTypeId] [int] NOT NULL                                             ->   [FirmId] [int] NOT NULL
)

Shouldn't it recognize that the two columns have the same name (FirmId) and type and prefer to map them and create the one with a new name (MethodTypeId)?

Thanks.
J

Comments

  • Options
    Hi,

    You could look at the script SQL Compare generates in this case to check whether the column is really being deleted then re-added. There can be situations where the UI does not match up lines in this way, but when deploying changes the column get left in place.

    You might be interested to know that we are looking into improving the user experience around viewing difference at the moment, so which differences will be deployed may be clearer in the future.

    Matthew Chandler
    Software Developer on SQL Compare and SQL Data Compare
    Matthew Chandler
    Software Developer on SQL Compare and SQL Data Compare
  • Options
    rlrcstrrlrcstr Posts: 9 Bronze 2
    Thanks for the response, Matthew. Looking forward to the improvements.
Sign In or Register to comment.