Post reply

The server is out of memory

  • January 24, 2005 at 3:02 am

    #109854

    We have MSAS dedicated server (2003 Server Edition), it has 5Gig memory and 11Gig virtual memory and we have followed Microsoft’s instructions to enabled it to address 3Gig of memory (boot.ini - multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /fastdetect /3GB). AS is running on SP3. Our minimum allocated memory is set to 1.792Gig and our memory conversion threshold is set to 1.984, and yes I’ve checked them in regedit.

    As soon as we up our settings to allow us to take advantage of 3Gig (even only to 2.048 and 2.240Gig respectively) we start to get out of memory errors.

    I’ve read the link http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/anservog.mspx#ETAA several times but it only warns about setting the threshold too low or too high with a ceiling of 2.7Gig, neither of which scenarios apply here.

    I’ve compared performance logs from both settings and cannot pinpoint the memory problem when the settings are above 2Gig.

    Can anybody point me in the right direction?

    Is this an indication that the 3Gig switch isn’t working?, if so how could I check?

  • January 24, 2005 at 1:44 pm

    #538820

    Don't know if this applies:

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;838840

    If not, maybe you want to search my site for "analysis". Should return 31 hits back to KB, MSDN and TechNet. Maybe it helps a bit.

    --
    Frank Kalis
    Microsoft SQL Server MVP
    Webmaster: http://www.insidesql.org/blogs
    My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

  • January 25, 2005 at 5:52 am

    #538920

    You need the /PAE switch in your BOOT.INI.  Without this, Windows will ignore everything above the 4GB line.

    The MS KB articles are a bit ambiguous about the need for /PAE on W2003 with certain hardware, but we have confirmed it is needed on our HP boxes.

    Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.

    When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara

  • January 25, 2005 at 7:34 am

    #538943

    I'm assuming you're running SQL Server on this server.  If so, you may want to take a look at the AWE enabled configuration option for SQL Server. 

  • January 27, 2005 at 3:48 am

    #539300

    I've enabled the /PAE switch and bumped up my threshold to 2.7Gig and as of yet (2 days) not had any memory problems.

    Thanks for the help nice people.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply