This article describes an issue when a database that contains a table or an indexed view that has a FULLTEXT INDEX is synchronized with an empty database. The generated synchronization script contains errors.
The user chooses an empty database as a destination:
After comparison in the results grid the user chooses all database objects and clicks the Synchronize button:
The generated synchronization script is executed with errors:
If an object (a table or an indexed view) has a FULLTEXT INDEX the script execution generates an error because the creation order is incorrect and an object is created before the FULLTEXT INDEX. The FULLTEXT INDEX cannot be created in the transaction and it’s created at the end of the synchronization script.
If a script contains an object that depends on a FULLTEXT INDEX change the order of object’s creation manually.
ApexSQL Diff 2013.01.0286 and older
ApexSQL is currently working to fix this issue permanently