This policy determines which accounts can use processes to keep data in the physical memory, thus preventing the system from paging data to the virtual memory of the disk. In SQL Server 2005, the "Lock Memory Page" option is set to off by default. If you have System Administrator privileges, you can use the Windows Group policy tool (gpedit. MSC) to manually enable this option and assign this permission to the account that is running SQL Server.
For more information about how to enable the "Lock Memory Page" option, see how to enable the "Lock Pages In Memory" option (Windows ).
Although there are no requirements, we recommend that you Lock pages in the memory when using a 64-bit operating system. For 32-bit operating systems, you must grant the "Lock Memory Page" permission before configuring awe for SQL Server.
How to enable the "Lock Memory Page" option (Windows)
By default, the Windows Policy "locking the memory page" is disabled". You must enable this permission to configure the address window extension (AWE ). This policy determines which accounts can use processes to keep data in the physical memory, thus preventing the system from paging data to the virtual memory of the disk. In a 32-bit operating system, setting this permission without awe significantly reduces system performance. You do not need to lock pages in the memory on a 64-bit operating system.
Use the Windows Group policy tool (gpedit. MSC) to enable this policy for the account used by SQL Server. You must be a system administrator to change this policy.
For tables that list the maximum Server Memory values, see memory architecture.
Enable the "Lock Pages In Memory" option
In"Start"Click"Run". In"Open"Box, type
Gpedit. MSC.
Will open"Group Policy"Dialog box.
In"Group Policy"Console, expand"Computer Configuration", And then expand"Windows Settings".
Expand"Security Settings", And then expand"Local Policy".
Select"User Rights Assignment"Folder.
The details pane displays the policy.
In this pane, double-click"Locking pages in memory".
In"Local Security Policy Settings"In the dialog box, click"Add"Button.
In"Select user or group"In the dialog box, add an account that has the permission to run sqlservr.exe.