I have no clue what to set up more. I tried a lot.

My Problem is that on my test Server everything is runing perfectly see enter image description here

but on my production Server its not! see enter image description here

I found this on my Production Server: "Using locked pages for buffer pool"

This is shown in the error log of the SQL Server. This line only Shows up in the production System.

Both Systems are SQL 2008 R2 Enterprise with WIN2K8 R2 both in 64 bit.

Locked Pages in Memory is not enabled in GPEDIT.MSC

Can someone explain that to me?


AWE allocated pages are not reported by Task Manager. The "Using locked pages for buffer pool" message means the production server is using AWE. Do not trust Task Manager. Use SQL Server own counters: SQL Server, Memory Manager Object, SQL Server, Buffer Manager Object.

Read Fun with Locked Pages, AWE, Task Manager, and the Working Set…

| improve this answer | |
  • 2
    I recommend you read the articles I linked. They explain everything well beyond 'nice try'. – Remus Rusanu Mar 25 '14 at 13:53
  • I dont want to read articles about Locked Pages since this is not my issue, or is it? – Philipp Mar 25 '14 at 14:14
  • 1
    Thanks Phillip, you just made my day, I literally burst into laugh. – Remus Rusanu Mar 25 '14 at 14:16
  • as far as i know "locked Pages in Memmory" aka "LPIM" as set in the gpedit. This is not set. So the Locked Pages should not be the issue or do i get something wrong here. Furthermore as far as I understood it, enable LPIM would increase virtual disk Memory or is it the otherway around. Furhtermore on the test System the LPIM is not enabled either. So again as far a I understand it, they should behave the same way?!?!? – Philipp Mar 25 '14 at 14:29
  • LPIM is a privilege that is already granted to certain accounts (eg. Local System). If the engine prints that in the errorlog, it means it successfully enabled the privilege. I must trust the engine message more than anything you say, sry. If LPIM is enabled, the engine will use AWE methods to allocate memory that the Task Manager does not report. For a correct view, just look at the SQL Server's own counters, as I suggested. – Remus Rusanu Mar 25 '14 at 14:43

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.