Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Unexpected behavior occurs when you run many processes on a computer that is running SQL Server
Article ID: 824422 - View products that this article applies to.
When many processes run on your computer (for example, more than 50), behaviors that were not expected may occur. However, you may or may not receive an error message, and the error messages that are associated the problem may not be logged in the log files on your computer. The following symptoms are associated with this problem:
To work around this problem, follow these steps.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
This problem is caused by a known problem in Microsoft Windows NT Server. SQL Server uses a non-interactive desktop heap. The non-interactive desktop heap may run out of memory if many processes are created. When there is not sufficient memory to satisfy an allocation request, an error is returned and the user is notified that the computer is low on memory. Some programs may not handle the failure, and sometimes there may not be sufficient memory to create the error message dialog box. When there is not sufficient memory to create the error message dialog box, the requested operation may fail without generating an error message.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/126962/ )"Out of memory" error message appears when you have a large number of programs running
Article ID: 824422 - Last Review: March 4, 2004 - Revision: 1.6