The full-text population on table '%1!s!' cannot be started because the full-text catalog is importing data from existing catalogs. After the import operation finishes, rerun the command.
the full-text for , which in full-text indexing on table ' '. After this change, will no longer participate in the table's ...
The full-text index cannot be created because filegroup '%1!s!' does not exist or the filegroup name is incorrectly specified. ...
The full-text index on table '{0}.{1}' will not be scripted for article '{2}' because it references the unpublished unique ...
The full-text indexing pipeline could not be initialized. This might be because the resources on the system are too low to ...
The full-text population on table '%1!s!' cannot be started because the full-text catalog is importing data from existing ...
The full-text protocol handler component '%1!s!' used to populate catalog '%2!s!' in a previous SQL Server release is not ...
The full-text query did not use the value specified for the OPTIMIZE FOR query hint. Only single terms are allowed as values ...
The full-text query has a very complex NEAR clause in the CONTAINS predicate or CONTAINSTABLE function. To ensure that a ...
The full-text word-breaker component '%1!s!' used to populate catalog '%2!s!' in a previous SQL Server release is not the ...