Microsoft KB Archive/923624

= FIX: Error message when you run an application against SQL Server 2005 that uses many unique user logins or performs many user login impersonations: &quot;insufficient system memory to run this query&quot; =

Article ID: 923624

Article Last Modified on 11/20/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Standard X64 Edition
 * Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Enterprise X64 Edition
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Developer Edition

-



Bug #: 1115 (SQL Hotfix)



Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.



SUMMARY
This article describes the following about this hotfix release:
 * The issues that are fixed by this hotfix package
 * The prerequisites for applying this hotfix package
 * Whether you must restart the computer after you apply this hotfix package
 * Whether this hotfix package is replaced by any other hotfix package
 * Whether you must make any registry changes after you apply this hotfix package
 * The files that are contained in this hotfix package



SYMPTOMS
When you run an application against SQL Server 2005, you may receive an error message that resembles the following:

2006-05-31 05:22:14.31 spid51 Error: 701, Severity: 17, State: 193.

2006-05-31 05:22:14.31 spid51 There is insufficient system memory to run this query.

This problem may occur if the application uses many unique user logins or performs many user login impersonations.

When this problem occurs, you may also see a high allocation value for the SinglePage Allocator counter of the USERSTORE_TOKENPERM command statements in the DBCC MemoryStatus statement. The following message is an example that shows a high allocation value in the USERSTORE_TOKENPERM command statement.

USERSTORE_TOKENPERM (Total)

VM Reserved = 0 KB

VM Committed = 0 KB

AWE Allocated = 0 KB

SM Reserved = 0 KB

SM Committed = 0 KB

SinglePage Allocator = 1414456 KB.

MultiPage Allocator = 0 KB

Note This problem may occur when you are using any edition of SQL Server 2005. However, this problem is more likely to occur when you are using Microsoft SQL Server 2005 Express Edition.



Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
 Microsoft SQL Server 2005 Service Pack 1 (SP1)

For more information about how to obtain SQL Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

913089 How to obtain the latest service pack for SQL Server 2005



Restart information
You do not have to restart the computer after you apply this hotfix.

Registry information
You do not have to change the registry after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.

SQL Server 2005 hotfix, 64-bit for Itanium processors


WORKAROUND
To work around this problem, stop and then restart SQL Server 2005.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Keywords: kbtshoot kbbug kbfix kbqfe kbpubtypekc kbhotfixserver KB923624

-

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

© Microsoft Corporation. All rights reserved.