Max Memory Setting

  • Hi

    I have seen a few post where people have a similar issue but no one has really provided a suitable answer hence my post.

    I have two environments both windows 2003 64bit enterprise, both SQL enterprise 64 bit both have 128GB of RAM both have sql sp3 the difference is one is a live production environment and the other is a dev environment.

    On my live environment SQL conforms to the max memory of 120GB I have set and will not go above this usage. My dev server however is ignoring this setting I have set it to 118 GB of RAM but continually goes up to just under 128. Which subsequently leaves no memory for IIS causing out of memory errors?

    The only difference I can see is that my live environment used a windows R2 and my dev environment didn’t use R2 to install windows, I can’t imagine why this would be the cause but I am clutching at straws is this the possible cause???? Any thoughts please guys.

  • Hi,

    I have a question. After you set the max memory, have you restarted the mssql service?

    Wish you good ideas! 🙂
    Andreea

  • Hi Yes sql service restarted even went for a server reboot.

    I have also tried this using the interface and scripting it followed by restarts but nothing works

  • What value have you written there?

    Wish you good ideas! 🙂
    Andreea

  • I have set it to 118 GB of RAM but continually goes up to just under 128

  • 118 GB = 120832 MB and that's the value you entered in the Maximum Server Memory box?

    Hmmm... I'll check why is this happening

    Wish you good ideas! 🙂
    Andreea

  • Yes it is set to 120832

  • If you haven't configured it using Reconfigure statement, try again using:

    SP_CONFIGURE “Max Server Memory”, 120832;RECONFIGURE;

    Even if as far as I know, a restart is not necessary, if possible, restart again the server.

    Let us know if the problem is still there :blink:

    Wish you good ideas! 🙂
    Andreea

  • Hi I have already tried this

Viewing 9 posts - 1 through 8 (of 8 total)

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