Symptom

When SQL Server's Full Text Search (a database-side indexing, not to be confused with ClearQuest Full-Text Search) feature is enabled against a table, the ClearQuest query wizard will generate SQL in a different manner when the operator "contains" is used for a SQL Server database with SQL Server FTS vs. SQL with SQL Server FTS unenabled.

Non-SQL Server FTS enabled record types would have a SQL statement based on the SQL "like" operator with a % wildcard:
select T1.dbid,T1.id,T1.description,T1.headline from Defect T1 where T1.dbid <> 0 and ((T1.description like '%this is my search text%'))

When SQL FTS is enabled, the SQL statement is written using the SQL "contains" operator and uses a different wildcard:
select T1.dbid,T1.id,T1.description,T1.headline from Defect T1 where T1.dbid <> 0 and contains(T1.description, '"this is my search text*"')

These two different statements return different results.

When enabling SQL Server FTS, it is best to only search for a single term. When searching for multiple terms such as this example: "this is my search text" you may receive no hits.