Post reply

SQL Compare 10

  • September 12, 2012 at 5:15 pm

    #147473

    Working with SQL Compare 10 to build upgrade scripts we have found that SQL Compare will map columns of different names that are the same data type and the same ordinal position in the column order.

    We can correct this, unmap these columns, manually but I am wondering if there is a setting some where that can be set (or unset) to prevent this behaviour.

    Our problem is that SQL Compare is mapping a column (or columns) that exist in one schema but was dropped in the other to a column that didn't exist in the first schema but added in the second and happen to have the same data type and are now in the same ordinal position as well.

  • September 13, 2012 at 4:00 pm

    #1537535

    Mail redgate support?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • September 13, 2012 at 4:07 pm

    #1537542

    GilaMonster (9/13/2012)

    Mail redgate support?

    Probably should, just hoping someone else had already dealt with this issue.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply