SQL Compare

Latest version: 10.0

SQL Compare

Knowledge Base

Stored procedures using full-text queries fail to synchronize

Category: Troubleshooting & error messages
Date: 04 Mar 2009
Product: SQL Compare
Versions: 3-8

When a SQL Compare synchronization script is run against a database that is full-text enabled, the following error may result:

Cannot use CONTAINS or FREETEXT predicate on table [table] because it is not full-text indexed

This is an outstanding issue in SQL Compare that is caused by an inability to include full-text queries inside a transaction. For this reason, any full-text indexes are created at the end of the synchronization script, which is more than likely going to be after the stored procedures are created.

The only practical workaround is to attempt to run this script, identify the stored procedure that cannot be created, find the offending table, and use SQL Compare to migrate this table by itself first. Next, recompare the databases and generate a new synchronization script. The table and full-text indexes should now be in place when the stored procedure is created or altered.

Document ID: KB200707000070 Keywords: SQL,Compare, full-text, full, text, catalog, CONTAINS, FREETEXT,

Was this article helpful?

Search support
Forums
Visit the SQL Compare forum.

SQL Compare

all SQL products

all products