I have a table that works fine in full-text search until the last week. There are over seven million entries, and I see that it contains more than seven million entries in the full-text index.
But there’s nothing more in the search results than a week ago. I can see in the table the full-text properties of the index that the number of “pending” records is growing (maybe 30 thousand) today, probably corresponds to what it did not add to the index.
The first thing I checked was whether to enable the index. This is not so, so I turned it on, and the process that started "ALTER FULLTEXT INDEX" started to block all other requests on the server, so I killed it.
I have confirmed that the full-text indexing service has started and is starting automatically. I also confirmed that it automatically checks for changes, although turning from “Automatic” to “Manual” to “Off” does not seem to do anything but reset the number of queued results. (Returning to "Automatic" resets the number to 30,000.)
I tried rebuilding the full-text index, but for "Full" and "Incremental", it discards the message "there is already an index." "Update" says that "command completed successfully", but does not seem to have any effect.
The last thing I did today:
- disable full-text index
- rebuild a clustered index based on FTI
- turn on FTI again
"ALTER FULLTEXT INDEX", , .
A: FTI , B: disable/rebuild/re-enable, , , - . ( B A, , A .)
? , ?