SQL Compare

Latest version: 10.0

SQL Compare

Knowledge Base

When does the synchronization process rebuild tables?

Category: How do I?
Date: 11 Mar 2010
Product: SQL Compare
SQL Compare will alter existing tables whenever possible when it synchronizes database schema. In some circumstances, however, the entire table must be dropped and recreated. This process involves creating a new table, copying all of the data to the new table, and dropping the old table. These are the circumstances which will cause this behavior:

· Changing an IDENTITY seed or increment value or dropping the IDENTITY property from a column
  · Adding a column in the middle of a table when the 'force column order' option is enabled
  · When you add/alter/drop PERSISTED computed columns
  · When it is impossible to implicitly cast one data type to another (e.g. DECIMAL to NUMERIC)
  · Changing the filegroup specification for a table
  · Changing partitioned columns
  · Adding a column that has no default and does not accept NULL values
  · Azure: When an ALTER COLUMN will cause a Primary Key or clustered index to be dropped and data exists in the table

Document ID: KB200708000113 Keywords: SQL,Compare,table,drop,rebuild,ALTER,create,data,copy

Was this article helpful?

Search support
Forums
Visit the SQL Compare forum.

SQL Compare

all SQL products

all products