During schema deployment, dbForge Studio for SQL Server updates existing tables when possible. In some cases, the tool must drop and recreate the table. In this process, it creates a new table, copies the data, and then deletes the old table.
The following table lists the cases that require a table rebuild.
| Case | Explanation |
|---|---|
An IDENTITY seed or increment value is changed, or the IDENTITY property is removed from a column. |
dbForge Studio rebuilds the table when you change an IDENTITY seed or increment value, or when you remove the IDENTITY property. Data is copied to a new table and then restored. |
| A column is inserted in the middle of a table when the Force Column Order option is enabled. | dbForge Studio rebuilds the table when you insert a column at a specific position in the column order while Force Column Order is enabled. |
| The filegroup specification for a table is changed. | dbForge Studio rebuilds the table when you change the filegroup. |
| Partitioned columns are changed. | dbForge Studio rebuilds the table when you modify a column that participates in partitioning. |
| A Primary Key is removed from a table. | Applies only to Azure SQL Database: dbForge Studio rebuilds the table when you drop a primary key or clustered index while the table contains data. |