Windows 2008 R2 | SQL 2008 R2 Express 64 bit - Info required about AWE, Locked pages to understand Memory usage


I was setting up a test lab to understand SQL server 2008 64 bit AWE/Lock pages feature and how it would effect Windows 2008 R2 server

My server config : I have 2 CPUS & 8 GB RAM

setup  SQL 2008 R2 Express 64 bit with instance name sqlexpress
enabled AWE, Set 5 GB of RAM as Minimum & Maximum
When i checked in taskmanger the memory usage is around 200 MB for sqlservr.exe process
And overall Physical Memory usgae is 600 MB
restarted my test server no luck
AM I missing something how to make SQL lock 5 GB which was allocated to it using AWE, Lock memory
Any help is highly appreciated

I tried using below command and also tried GUI
USE master
sp_configure 'show advanced options', 1
EXEC sp_configure 'min server memory', 680 -- 2 GB min, replace with your desired amount here
EXEC sp_configure 'max server memory', 680 -- 6 GB min, replace with your desired amount here

USE master -- database name
sp_configure 'show advanced options', 1
sp_configure 'awe enabled', 1

Thanks in Advance
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Robert SchuttSoftware EngineerCommented:
It looks like you only changed the comment, try changing 680 to 2048 for example:
EXEC sp_configure 'min server memory', 2048 -- 2 GB min, replace with your desired amount here

Open in new window

(same goes for max)
Robert SchuttSoftware EngineerCommented:
BTW, max with express may be 2 (or even 1) GB, and AWE not applicable, not sure though...

I was reading this:
techieeguyAuthor Commented:
Thanks for your quick response

sorry to post wrong command i did change them to 5 GB when i tried pls refer attached screenshots sql02.jpg & sql03.jpg  sql instance sqlexpress server properties -> Memory and from my task manager
current physical usage is 1 gb
OWASP: Avoiding Hacker Tricks

Learn to build secure applications from the mindset of the hacker and avoid being exploited.

techieeguyAuthor Commented:
Hi Robert Schutt
I saw your 2nd comment and the blog pls disregard my above comment the blog provided by you does makes sense seems SQL express will not cross 1GB

Could you confirm if i did the same with a sql server this command will work and i can lock pages i will try with sql if it requires
Anthony PerkinsCommented:
If you are trying to lock pages in memory, you are not going about it the right way.  This is how you do it: How to: Enable the Lock Pages in Memory Option (Windows)
Robert SchuttSoftware EngineerCommented:
Yes, with a full version it should work. Still, depending on the SQL Server version, you may hit the old restrictions (2 or 3 GB).

I must admit I haven't worked with this option myself, only responded to the obvious mistake you seemed to have made...

By the way, in the page linked by @acperkins it says:
Locking pages in memory is not required on 64-bit operating systems.
And in a link from that page Memory Architecture it says:
Support for AWE is available only in the SQL Server Enterprise, Standard, and Developer editions and only applies to 32-bit operating systems
Maybe you need to elaborate on why you think you need to lock pages and use AWE.

Here's my simplistic view: if you have a dedicated database server that has little else to do and you have enough memory to fit most of your regularly used data in it, SQL Server will already keep the data needed to work most efficiently in memory.

A good database design and application architecture (with smart use of SQL queries) will go a long way to support that and you should not have to resort to any 'low-level' trickery to make SQL Server faster.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Anthony PerkinsCommented:
Locking pages in memory is not required on 64-bit operating systems.
This is not as cut and dried as MS would like us to think.  There is a lot of debate on this among the leading SQL Server MVPs.  Let me know if you need blogs on this subject and I can search for them.
techieeguyAuthor Commented:
Sorry for delayed response
just download sql 2012 iso which was 3.6 GB size and installed 64 bit, yeah AWE option is not there but lock pages can still be enabled as per "Anthony Perkins" blog by using group policy.

To enable the lock pages in memory option using group policy

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

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

    Expand Security Settings, and then expand Local Policies.

    Select the User Rights Assignment folder.

    The policies will be displayed in the details pane.

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

    In the Local Security Setting – Lock pages in memory dialog box, click Add User or Group.

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

    Log out and then log back in for this change to take effect.

I have 2 days off from tomorrow, i am trying from some script or way to grow my database above 4 gb and check if lock pages are visible using Rammap and Vmmap.

What i am basically trying to achieve is to understand this feature as i could see some times we are unable to track/monitor memory usage of windows server due to this,

I tried reading lot of material and spent lot of time still unable to understand how this works. Any blog with steps to achive above is good enough. I don't want to waste your time so any good material will do and i can close this question :)
Robert SchuttSoftware EngineerCommented:
one of my favorite sql websites is, I searched there and found links to pages mentioned in earlier posts, but also to where, under the heading "Improvements in Windows Server 2008 and in Windows Server 2008 R2" (near the bottom), you find some more (hopefully interesting) info about why it shouldn't be necessary although the goal of the page seems to be explain how to do it anyway.
Seth SimmonsSr. Systems AdministratorCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.