June 28, 2010 at 5:00 pm
I'm starting to get a server is out of memory error (MSSQLServerOLAPService Event ID: 123). I'm running SQL Server 2008 on Windows Server 2003 Enterprise Edition with 16 MB of RAM, the CPU is a Xeon E5430 @ 2.66GHz (doubt the CPU matters!). The OS is x86 bit (NOT x64 bit). In the Server Properties in the Memory section the Maximum server memory was already set to 12288 MB (12 GB). The 'Use AWE to allocate memory' option is not checked. From what I understand on this x86 OS, SQL Server won't use over 2GB of RAM without AWE right? So is that 'Max server memory' setting at 12GB useless without AWE enabled? Don't they have to go hand in hand? Thanks for the input!
June 28, 2010 at 5:10 pm
Correct, with this setup for SQL to use memory above 4Gb you need to enable AWE. Also allocate the 'lock pages in memory' right to the SQL service account.
Its not the SQL engine that is complaining about memory shortage though, its analysis services.
---------------------------------------------------------------------
June 28, 2010 at 5:15 pm
george sibbald (6/28/2010)
Correct, with this setup for SQL to use memory above 4Gb you need to enable AWE. Also allocate the 'lock pages in memory' right to the SQL service account.Its not the SQL engine that is complaining about memory shortage though, its analysis services.
Ok thanks. And you mention analysis services is having the memory shortage. I was worried about that because I read here in the yellow shaded note that "Analysis Services cannot take advantage of AWE mapped memory." What's the best way to get rid of this memory error?
June 29, 2010 at 3:42 am
Greg_ (6/28/2010)
george sibbald (6/28/2010)
Correct, with this setup for SQL to use memory above 4Gb you need to enable AWE. Also allocate the 'lock pages in memory' right to the SQL service account.Its not the SQL engine that is complaining about memory shortage though, its analysis services.
Ok thanks. And you mention analysis services is having the memory shortage. I was worried about that because I read here in the yellow shaded note that "Analysis Services cannot take advantage of AWE mapped memory." What's the best way to get rid of this memory error?
thats a difficult question, especially as I am no expert in SSAS. Check your boot.ini file see if the /3GB switch is set, if it is remove it. I would still go ahead with setting AWE for SQL, but cap the max memory at 12 -13GB.
You would have to try and identify the SSAS process consuming the memory, not sure how though. If SSAS is heavily used it does not sit well with the SQL engine on a 32bit system, so you could be forced into an upgrade to 64 bit or moving SSAS off to its own server. Second option will have a hit on network traffic though.
---------------------------------------------------------------------
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply