Data preservation revisited

slag

If a column has been inserted, the option 'force column order to be identical' will indicate to SQLCompare to Rebuild a table instead of Altering It.

Else than that, in what other circumstances would SQLCompare Rebuild a table?

Thanks

Brian Donahue

Hello,

Changing an IDENTITY column will do it, for one. You can see this in the WidgetProduction and WidgetStaging examples in the SQL Compare help file. Otherwise I don't have a complete set of circumstances handy.

Brian Donahue

I take that back. There are many examples in the new SQL Compare help file under the heading warnings:

SQL Compare rebuilds a table when:

• a table's filegroup has changed
  You can ignore filegroups by selecting the Ignore file groups comparison option. By default, filegroups are ignored.
• a column cannot be altered
  For example, this warning is displayed if a column is to be changed from data type text to varchar.
• a property of a column cannot be altered
  For example, this warning is displayed if a column is an identity in one database but not in the other.
• the identity column on a table has changed
  For example, this warning is displayed if the seed has changed.
• the column order on a table has changed
  This warning is displayed only if Force table column order to be identical is selected in your Comparison Options and the order of columns in a table has changed. To ignore column order, clear the option.
• column x on table y must be added but has no default and does not allow NULL values
  If the table contains data, the synchronization script will not work. To avoid this, add a default to the column in the source database, or set it to allow NULL values.
• column x on table y must be added and does not allow NULL values; the default z must be bound to it
• A table in the source database contains an additional column that is set to NOT NULL, and has a default set.