Extended property granularity

ccollinsccollins Posts: 64
edited January 12, 2007 6:09PM in SQL Toolkit Previous Versions
The extended property differences are not an item in the differences collection. Is there another way of controlling, (i.e. setting an extended property difference.selected to false), extended properties individually, both at the database and table level?

Working need:
Exclude a specific database level extended property from work.BuildFromDifferences and the resulting synchronization.

Comments

  • Brian DonahueBrian Donahue Posts: 6,590 Bronze 1
    Hello,

    Extended Properties are considered a property of the table object, so the only option I can see would help is to set the IgnoreExtendedProperties option in your options enumeration. This would stop the comparison and synchronization of all extended properties.
  • So the database level extend properties are considered part of what object?

    We cannot ignore the table level properties, they need to be synchronized.

    We cannot ignore all of the database level properties, all but one needs to be synchronized.
  • Brian DonahueBrian Donahue Posts: 6,590 Bronze 1
    It's still an all-or-nothing proposition, unfortunately.
Sign In or Register to comment.