SQL Server 2008 Books Online (October 2009)
How to: Enable the Lock Pages in Memory Option (Windows)

The Windows policy Lock Pages in Memory option is disabled by default. This privilege must be enabled to configure Address Windowing Extensions (AWE). This policy determines which accounts can use a process to keep data in physical memory, preventing the system from paging the data to virtual memory on disk. On 32-bit operating systems, setting this privilege when not using AWE can significantly impair system performance. Locking pages in memory is not required on 64-bit operating systems.

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 a table that lists the maximum server memory values, see Memory Architecture.

To enable the lock pages in memory option

  1. On the Start menu, click Run. In the Open box, type gpedit.msc.

    The Group Policy dialog box opens.

  2. On the Group Policy console, expand Computer Configuration, and then expand Windows Settings.

  3. Expand Security Settings, and then expand Local Policies.

  4. Select the User Rights Assignment folder.

    The policies will be displayed in the details pane.

  5. In the pane, double-click Lock pages in memory.

  6. In the Local Security Policy Setting dialog box, click Add.

  7. In the Select Users or Groups dialog box, add an account with privileges to run sqlservr.exe.

See Also

Tasks

How to: Configure the awe enabled Option (SQL Server Management Studio)

Concepts

awe enabled Option

Other Resources

Using AWE

Help and Information

Getting SQL Server 2008 Assistance
Tags :


Community Content

DBA James
Locking Pages in 64-bit may be required...
Although this page states " Locking pages in memory is not required on 64-bit operating systems.", there is a KB article that contradicts this statement (as well as error messages that may appear in SQL Server 2005+ logs that state the sqlserver process memory has been paged out), called "How to reduce paging of buffer pool memory in the 64-bit version of SQL Server". Reference KB Article # 918483 (http://support.microsoft.com/KB/918483/EN-US).

Chris Lively
Why you want this enabled
Along with DBA James finding, here is a blog post which talks about the performance gain by using locked pages
http://blogs.msdn.com/slavao/archive/2005/04/29/413425.aspx

and here is one that explains why AWE is still around on 64 bit systems and why locked pages are actually a preferred mechanism for memory management.
http://blogs.msdn.com/psssql/archive/2009/09/11/fun-with-locked-pages-awe-task-manager-and-the-working-set.aspx

Page view tracker