Warren Peace (8/6/2009)
Carve out in SQL to start at 12GB and max out at 14GB. Then set your locked pages policy to the account SQL is running under. Make sure to put a check in the check box Use AWE to allocate memory in the "Memory" page and in the "Processors" page put a check box in the "Boost SQL Server priority".
First, AWE is not an option on x64 hardware because it is not needed. You don't have to check the box to enable it - it is not recognized on x64 systems.
Second, for a dedicated database server there is no reason to set a minimum memory amount. Setting the minimum to 12GB and the maximum to 14GB running SQL Server 2005 Standard Edition (x64) will almost certainly cause memory pressure on the system.
Third, SQL Server 2005 Standard Edition (x64) cannot lock pages in memory. Setting the policy is a good idea, but it will not make any difference using this edition. There is a patch on the way that will change this behavior but it is not out yet.
And finally, DO NOT 'Boost SQL Server Priority' unless you are working directly with MS (PSS Engineers). And only then if you are addressing a specific issue with a specific version of an application that has been tested and shown to correct a problem.
Again, using SQL Server 2005 Standard Edition (x64) you don't want to set a max memory greater than 12GB. You can try upping that to 13GB but be prepared to monitor the server for memory pressure.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs