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

SQL Compare generating different scripts

sehuff1203sehuff1203 Posts: 3 New member
edited November 5, 2015 1:45PM in SQL Compare Previous Versions
My and a co-worker are both running SQL Compare

From what I can tell our settings are the same.

If we compare the same two databases, let's say A => B

A is adding a new field to an existing table with existing data that is a BIT field.

When I run the compare SQL Compare automatically sets a default value of (0) to apply to database B for that new field - which makes since otherwise there will be a problem since it has data in it already and we are saying that field can't be null.

However - we didn't specifically set the default value to (0) in database A.

When my co-worker runs the comparison with SQL Compare on their machine - it does not automatically set the default value of (0) when it generates the script and when you try to apply it you get a warning and of course the script doesn't work.

Why does the script generate differently on two different machines?


  • Options

    Thanks for your question on SQL Compare. One thing that could be different from machines is the options and mappings done, so make sure both machines are say using the defaults and that both are deploying all dependencies and then see if the scripts are still different, thanks.
    Allen LeVan
    Red Gate Software
    US Product Support
Sign In or Register to comment.