Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 811891 - Last Review: April 12, 2006 - Revision: 4.2
SQL Server only uses 2 GB of memory even though the AWE option is enabled
SYMPTOMS
SQL Server only uses 2 gigabytes (GB) of memory even though
SQL Server is configured to use the Microsoft Windows 2000 Address Windowing
Extensions (AWE) API to support a maximum of 64 GB of physical memory when the
awe enabled option is set to 1. Windows Task Manager also shows that SQL
Server is using only 2 GB of memory.
In the SQL Server log, you will
see the following message:
Cannot use Address
Windowing Extensions because lock memory privilege was not
granted.
CAUSE
The user account the SQL Server service is running on was
not added to the
Lock Page in Memory policy of the
User Rights Assignments in the
Local Security Policy of the computer.
RESOLUTION
To resolve this problem, follow these steps:
Note: You can only perform these tasks at the individual server
console. To perform these tasks, you must log on to Windows as a local
administrator on the computer where SQL Server exists.
- On the Taskbar, click Start, and then
click Programs.
- Click Administrative Tools, and then
select Local Security Policy.
- Expand Security Settings, expand
Local Policies, and then click User Rights
Assignments.
- In the right screen, right-click Lock pages in
memory, and then click Security.
- In the Local Security Policy Setting
dialog box, click Add.
- Click to select the account where the MSSQLSERVER service
is running.
- Click OK.
- For Microsoft Windows 2000 Server, in the command window, type Secedit /refreshpolicy machine_policy /enforce. For Microsoft Windows Server 2003, in the command window, type GPUPDATE /force.
- Restart the SQL Server service.
MORE INFORMATION
If your instance of SQL Server is installed on a computer that is running Windows 2000 Advanced Server, Windows 2000 Datacenter Edition, Windows Server 2003, or Windows NT, you can use the
/3GB switch in the Boot.ini file on your computer. As a result, SQL Server 2000 can use up to 3 GB of available memory on your computer.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
274750Â
(http://kbalertz.com/Feedback.aspx?kbNumber=274750/
)
How to configure SQL Server to use more than 2 GB of physical memory
REFERENCES
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
329914Â
(http://kbalertz.com/Feedback.aspx?kbNumber=329914/
)
AWE-enabled SQL Server 2000 may take a long time to start
298444Â
(http://kbalertz.com/Feedback.aspx?kbNumber=298444/
)
A description of the Group Policy Update utility
APPLIES TO
- Microsoft SQL Server 2000 Enterprise Edition
- Microsoft Windows 2000 Advanced Server
- Microsoft SQL Server 2005 Enterprise Edition
| kbsysadmin kbsecurity kbprb KB811891 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please