Article ID: 811891 - View products that this article applies to.
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:
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.
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.
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:
(https://support.microsoft.com/kb/274750/ )How to configure SQL Server to use more than 2 GB of physical memory
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/329914/ )AWE-enabled SQL Server 2000 may take a long time to start
(https://support.microsoft.com/kb/298444/ )A description of the Group Policy Update utility
Article ID: 811891 - Last Review: April 12, 2006 - Revision: 4.2