The full-text filter component '%1!s!' used to populate catalog '%2!s!' in a previous SQL Server release is not the current version (component version is '%3!s!', full path is '%4!s!'). This may cause search results to differ slightly from previous releases. To avoid this, rebuild the full-text catalog using the current version of the filter component.
The Full aggregation usage setting should be avoided in cases where an attribute contains a large number of members. If specified ...
The full-text catalog '%1!s!' (%2!s!) in database '%3!s!' (%4!s!) will be remounted to recover from a failure. Reason code: ...
The full-text catalog health monitor reported a failure for full-text catalog '%1!s!' (%2!s!) in database '%3!s!' (%4!s!). ...
The full-text catalog monitor reported catalog '%1!s!' (%2!s!) in database '%3!s!' (%4!s!) in %5!s! state. This is an informational ...
The full-text filter component '%1!s!' used to populate catalog '%2!s!' in a previous SQL Server release is not the current ...
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 ...