FIX: Mssdmn.exe Process Uses All Available Memory When You Populate Full-Text Index

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


The population of a very large full-text index may cause the Mssdmn.exe process to use all of the available memory on the computer. As a result, the computer may stop responding (hang) so that it is inaccessible through the user interface.

To confirm that you are encountering this specific problem, start a Performance Monitor log before you populate the full-text index, and monitor the following items:
Performance Object: Process
Counter: Working Set
Instance: mssdmn
The Working Set counter corresponds to the memory usage of a process. If you are encountering this specific problem, the memory usage (Working Set) for this instance steadily increases. You can also view this information in Task Manager under the Mssdmn.exe process on the Processes tab.


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


Microsoft has confirmed that this is a problem in Microsoft SQL Server 2000. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.


The Mssdmn.exe process brings the text data from the SQL Server table to the full-text index.


Article ID: 308797 - Last Review: October 17, 2003 - Revision: 3.2
  • Microsoft SQL Server 2000 Standard Edition
kbbug kbfix KB308797

Give Feedback


Contact us for more help

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