FT_IFTS_SCHEDULER_IDLE_WAIT is recorded by the full-text search scheduler while it waits for work to appear on the full-text background task queue. If the Full-Text Engine is installed, this scheduler exists and mostly idles, whether or not any full-text indexes are defined or queried.
An idle scheduler measuring its own idleness, which is to say: another permanent background timer.
Is It a Problem?
No, and it can be safely ignored outright. It sits on the standard benign filter list, accumulates in proportion to uptime, and says nothing about full-text indexing performance even on systems that use the feature heavily.
Genuine full-text questions, crawl performance, index population lag, query speed, are answered through the full-text catalogs’ own properties and the crawl logs, not through the scheduler’s nap time.
Common Causes
- Full-text search components installed (very common), with the background scheduler idling.
- Little or no full-text crawl activity, which is most of the time on most systems.
What To Do
- Filter it out of wait analysis; our
Get-WaitStatisticsscript does by default. - For full-text performance work, check catalog population status (
FULLTEXTCATALOGPROPERTY) and the crawl logs in the instance’s log directory. - Spend zero tuning effort on this wait.
How To See It
Rank waits with Get-WaitStatistics; it is filtered. In raw output on full-text-enabled instances it is a fixture, and a meaningless one.
Part of the SQL Server Wait Types Library.
Related deep dive: SOS_SCHEDULER_YIELD Wait Type.
Leave a Reply