FIX: Mssearch.exe Memory Leak Occurs When Results Are Not Completely Processed

Article translations Article translations
Article ID: 296465 - View products that this article applies to.
This article was previously published under Q296465
BUG #: 353641 (SHILOH_BUGS)
Expand all | Collapse all

SYMPTOMS

The Mssearch.exe process may experience a private byte memory leak if the rowset is not fully consumed.

The memory leak may occur when you use SQL Server full-text queries if:

  • The Transact-SQL "TOP ##" or "set rowcount ##" restrictions are applied.

-or-

  • The query is cancelled before all the results are fetched by the client.

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

WORKAROUND

Avoid query cancellations and use of the Transact-SQL "TOP N" feature to make sure that all the rows are processed.

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 1.

Properties

Article ID: 296465 - Last Review: October 9, 2003 - Revision: 4.1
APPLIES TO
  • Microsoft SQL Server 2000 Standard Edition
Keywords: 
kbsqlserv2000sp1fix kbfix kbbug KB296465

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com