FIX: Mssearch.exe Memory Leak Occurs When Results Are Not Completely Processed (296465)
The information in this article applies to:
- Microsoft SQL Server 2000 (all editions)
This article was previously published under Q296465 BUG #: 353641 (SHILOH_BUGS) SYMPTOMSThe 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.
- 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. STATUSMicrosoft 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.
Modification Type: | Major | Last Reviewed: | 10/9/2003 |
---|
Keywords: | kbSQLServ2000sp1fix kbfix kbBug KB296465 |
---|
|