When I perform a Schema Compare and I run the Synchronization scripts, I get many different errors.
Here are some of the errors received:
1)
SQL Server Database Error: There is already an object named 'DF__Collectio__ItemI__4CAB505A' in the database.
Could not create constraint. See previous errors. 1636 0
2)
SQL Server Database Error: Invalid object name 'dbo.tmp_CollectionItems'. 1692 0
3)
SQL Server Database Error: No item by the name of '[dbo].[tmp_CollectionItems]' could be found in the current database 'ediscoBCBS', given that @itemtype was input as '(null)'. 1709 0
4)
SQL Server Database Error: Table 'CollectedDiskImages' already has a primary key defined on it.
Could not create constraint. See previous errors. 2259 0
5)
SQL Server Database Error: Cannot find the object "dbo.CollectedFiles" because it does not exist or you do not have permissions. 2274 0
6)
SQL Server Database Error: Table 'CollectedMailBoxFiles' already has a primary key defined on it.
Could not create constraint. See previous errors. 2289 0
7)
SQL Server Database Error: Column already has a DEFAULT bound to it.
Could not create constraint. See previous errors. 2312 0
Toad for SQL Server creates temporary tables for the tables that have data in it, and if the table has Constraints in it, Toad will use the same Constraint names as in the original table causing errors throughout the script.
WORKAROUND:
Rename the duplicate Constraint names in the script.
STATUS:
Waiting for fix in a future release of Toad for SQL Server.
