Table mismatch ((0)) versus (0) in column defaults

IanT8IanT8 Posts: 4
edited September 11, 2010 7:48AM in SQL Compare Previous Versions
Whilst preparing some database changes for a release into production on Friday, SQL Compare showed a table in the source database did not match the corresponding table in the production database.

On inspection, some columns had default values.

In the source table, the defaults were shown like this: ((0)) whereas in the target table as (0).

I tried to replace the double brackets using SSMS but it seemed impossible.

SQL Compare 8.2
SQL 2008 Developer v SQL 2008 Std

Any ideas why this might be happening. I'm not saying its a bug with SQL compare.

The database was originally created in SQL 2000 and has been moved over time to SQL 2005 and SQL 2008 and seems to be operating in 2008 compatibility level.
· Share on Twitter

Comments

  • David AtkinsonDavid Atkinson Posts: 1,458 Rose Gold 2
    This is a peculiarity about the way SQL Server scripts out the objects, which changed in SQL Server 2008. Although SQL Compare shows the difference in the difference panel (as this shows textual differences), it shouldn't be regarding it as a 'real' difference. Are you sure there isn't something else different if SQL Compare is picking this up and putting the object in the "objects that exist in both but are differe" grouping?

    David Atkinson
    Red Gate Software
    David Atkinson
    Product Manager
    Redgate Software
    · Share on Twitter
Sign In or Register to comment.