The full-text index is in an inconsistent state because the search property list of the full-text index was reconfigured using the WITH NO POPULATION clause. To bring the full-text index into a consistent state, start a full population using the statement ALTER FULLTEXT INDEX ONSTART FULL POPULATION;. This is a warning. No user action is necessary.
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 filter daemon host process has stopped normally. The process will be automatically restarted if necessary. ...
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 is in an inconsistent state because the search property list of the full-text index was reconfigured ...
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 ...