Full-text stoplist '%1!s!' cannot be dropped because it is being used by at least one full-text index. To identify which ...

SQL Server 2008

Full-text stoplist '%1!s!' cannot be dropped because it is being used by at least one full-text index. To identify which full-text index is using a stoplist: obtain the stoplist ID from the stoplist_id column of the sys.fulltext_indexes catalog view, and then look up that stoplist ID in the stoplist_id column of the sys.fulltext_stoplists catalog view. Either drop the full-text index by using DROP FULLTEXT INDEX or change its stoplist setting by using ALTER FULLTEXT INDEX. Then retry dropping the stoplist.

Full-text index for table or indexed view '%1!s!' cannot be populated because the database is in single-user access mode. ... Full-text predicates cannot appear in the %1!s! clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or ... Full-Text Search is not enabled for the current database. Use sp_fulltext_database to enable full-text search for the database. ... Full-Text Search is not enabled for the current database. Use sp_fulltext_database to enable Full-Text Search. The functionality ... Full-text stoplist '%1!s!' cannot be dropped because it is being used by at least one full-text index. To identify which ... Fulltext index error during compression or decompression. Full-text index may be corrupted on disk. Run dbcc checkdatabase ... Fulltext predicate references columns from two different tables or indexed views '%1!s!' and '%2!s!' which is not allowed. ... Function '%1!s!' is not allowed in the %2!s! clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE ... Function '%1!s!' is not allowed in the OUTPUT clause, because it performs user or system data access, or is assumed to perform ...