You may receive a 17883 error message when you run full-text queries in SQL Server 7.0 or SQL Server 2000 (888666)
The information in this article applies to:
- Microsoft SQL Server 2000 (all editions)
- Microsoft SQL Server 7.0
BUG #: 472695 (SQL Server 8.0)
SYMPTOMSWhen you run a full-text query in Microsoft SQL Server 2000,
the result set may not return in a short period if a catalog merge operation is
occurring at the same time. When this delay occurs, the SQL Server User Mode
Scheduler (UMS) may become unresponsive, and this could lead to stalled worker
request behavior. Additionally, you may receive an error message that is
similar to the following: Error: 17883, Severity: 1,
State: 0 The Scheduler %1!ld! appears to be hung. SPID %2!ld!, ECID %3! ld!,
UMS Context 0x%4!p!
WORKAROUNDTo work around this problem, use the following guidelines to
maintain your full-text catalogs.
- Avoid incremental updates to the catalog. Instead, use
change tracking to apply the full-text indexes changes.
- Disable background updates by running the sp_fulltext_table stored procedure with the stop_background_updateindex option. Instead of using background updates, use the update_index option at a scheduled time to apply the full-text index
changes.
- Use the FULLTEXTCATALOGPROPERTY function to monitor the
status of the catalog.
- Use the sp_fulltext_service stored procedure with the resource_usage option to increase the resource usage to a level of 5. The level
specifies the amount of resources to be used for the Microsoft Search Service
(MSSearch). By increasing the resource_usage value, faster catalog builds will occur.
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section.
Modification Type: | Major | Last Reviewed: | 12/17/2004 |
---|
Keywords: | kbtshoot kbprb KB888666 kbAudDeveloper kbAudITPRO |
---|
|