Microsoft KB Archive/888666: Difference between revisions
(importing KB archive) |
(No difference)
|
Latest revision as of 18:20, 18 July 2020
Article ID: 888666
Article Last Modified on 3/13/2007
APPLIES TO
- Microsoft SQL Server 2000 Standard Edition
- Microsoft SQL Server 7.0 Standard Edition
BUG #: 472695 (SQL Server 8.0)
SYMPTOMS
When 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:
WORKAROUND
To 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.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For more information about full-text queries in SQL Server, visit the following Microsoft Developer Network (MSDN) Web site:
For more information about how to optimize SQL Server full-text indexing, visit the following Microsoft Developer Network (MSDN) Web site:
Additional query words: SQL2000
Keywords: kbtshoot kbprb KB888666