Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I recently found out, that a server got a 32 bit installation of SQL Server 2012 rather than 64bit, and it is running out of memory now.

Can I have this 32 bit installation use more memory using locked pages?

I do not know much about this. I've read this bit I am still not clear if this will help, what needs to be done etc

share|improve this question
How long are you going to fight this thing, instead of doing the right thing and installing a proper, 64-bit instance? – Aaron Bertrand Dec 15 '13 at 16:00
32 bit still exists in serverland? – swasheck Dec 16 '13 at 2:31
we had trouble getting a 64 bit version on time, but we made it. – Greg Bala Dec 20 '13 at 22:29
up vote 7 down vote accepted

Can I have this 32 bit installation use more memory using locked pages?

In the past, my answer would have been (a heavily qualified) "yes".

Using AWE (address windowing extensions) would enable up to 64GB memory. Unfortunately (from your point of view, perhaps) 32-bit AWE was removed from the database engine starting with SQL Server 2012.

In previous versions, 32-bit SQL Server running on a 64-bit version of Windows (WOW mode) was a supported configuration but one that I never encountered personally. Anecdotally, such configurations were often problematic; if you enjoy tracking down weird problems, 32-bit AWE SQL Server on 64-bit Windows is for you.

My very strong recommendation would be to use 64-bit SQL Server 2012 instead.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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