Scenarios where the deployment process rebuilds tables
When dbForge Schema Compare for SQL Server deploys schema changes, it alters existing tables if possible. But sometimes the entire table must be dropped and recreated. In this case, a new table is created. Then all data is copied to the new table and the old one is deleted.
| Case | Explanation |
|---|---|
| An IDENTITY seed or increment value is changed, or the IDENTITY property is dropped from a column. | A table will be rebuilt, when you change an IDENTITY value or delete an IDENTITY properties from a target object. Data is transferred through a temporary table. |
| A column is added in the middle of a table when the “force column order” option is enabled. | A table will be rebuilt, if you add a column to the middle of the columns list with the “force column order” comparison option enabled. |
| The filegroup specification is changed for a table. | A table will be rebuilt, when you change a table filegroup. |
| The partitioned columns are changed. | A table will be rebuilt, when you change the partitioning of a table column. |
| A Primary Key is deleted from a table. | This case concerns only Azure SQL. A table will be rebuilt, when an ALTER COLUMN causes a Primary Key or clustered index to be dropped, but data exists in the table. |
Want to Find out More?
Overview
Take a quick tour to learn all about the key benefits delivered by dbForge Schema Compare for SQL Server.
All features
Get acquainted with the rich features and capabilities of the Schema Compare in less than 5 minutes.
Request a demo
If you consider employing the Schema Compare for your business, request a demo to see it in action.
Ready to start using dbForge Schema Compare for SQL Server?