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


Ben MillsBen Mills Posts: 50
This is a minor problem, but the dtproperties table always appears when I run a compare, even though the table exists on both the target and the source databases. I even tried running the sync with dtproperties checked once and I got an error saying that the table already exists on the target.


  • Options
    I too have been experiencing this same issue.
  • Options
    Brian DonahueBrian Donahue Posts: 6,590 Bronze 1

    The dtproperties table is a system table that SQL Compare really should ignore. The table is created the first time that you run a diagram on the database. What has been happing to some folks lately is that their dtproperties tables haven't been getting their 'System' bit set properly so that SQL Compare thinks they're 'User' tables.

    Yes, dtproperties always says it's a 'User' table in Enterprise Manager, but SQL Compare should ignore it because of some information in the sysobjects system table.

    This explains why dtproperties shows up in one database through SQL Compare but not the other. Something has changed the object properties of the dtproperties table.
This discussion has been closed.