Microsoft KB Archive/323039

= FIX: Full-Text Search Population of a Word Document Stored in SQL Server Causes CPU Spin with SQL Server 2000 Service Pack 2 =

Article ID: 323039

Article Last Modified on 2/19/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Service Pack 2

-



This article was previously published under Q323039



BUG #: 357644 (SHILOH_BUGS)



SYMPTOMS
After you apply SQL Server 2000 Service Pack 2, the time it takes to populate a full-text search (FTS) catalog that contains Microsoft Word documents may increase dramatically. During this time, the Mssdmn.exe search filter daemon may consume almost 100 percent of one CPU (on a multi-processor server this may appear as a percent of total processor time that is equivalent to a single CPU. For example, 25 percent on a four processor server). If you use the FULLTEXTCATALOGPROPERTY Transact-SQL function to query the state of the catalog, the PopulateStatus property remains at 1 or 6 (&quot;population in progress&quot;), and the ItemCount property and the UniqueKeyCount property do not increase for a period of hours. After several hours, the MSSearch service will issue a timeout and the population will stop; however, the catalog will not be fully populated.



RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 INF: How To Obtain the Latest SQL Server 2000 Service Pack

NOTE: The following hotfix was created before the release of Microsoft SQL Server 2000 Service Pack 3.

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.   Date          Time    Version       Size            File name

28-Jun-2002  19:04   2002.6.28.0   217,088 bytes   Offfilt.dll NOTE: Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

This problem was first corrected in Microsoft SQL Server 2000 Service Pack 3.



MORE INFORMATION
Another issue that is similar is described in the following Microsoft Knowledge Base article:

323038 FIX: Infinite Loop During Full-Text Catalog Population

You can use the following points to distinguish the issue described in Q323038 from the issue discussed in this article:


 * The issue described in this article will only appear on SQL Server 2000 Service Pack 2, while the issue in Q323038 may appear on any build of SQL Server 2000 up to and including SQL Server 2000 Service Pack 2.


 * If you experience the issue described in this article, population may run several hours longer than it should; however, the MSSearch will eventually timeout and cancel the population. If you experience the issue described in Q323038, the catalog population never completes.


 * In this issue, CPU utilization for the Mssdmn.exe process is higher than CPU utilization for Mssearch.exe. These roles are reversed for the issue described in Q323038.

Additional query words: CPU spin hang Full-Text fulltext slow performance infinite loop MSSearch SP2 regression SP 2

Keywords: kbqfe kbhotfixserver kbsqlserv2000sp3fix kbbug kbfix kbsqlserv2000presp3fix KB323039

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.