Post reply

SQL Memory settings

  • March 14, 2014 at 1:39 pm

    #289424

    Hi,

    I have SQL 2008 R2 installed on win2012 standard with 64 gig of ram. I have set sql to use 53 gig but task manager is only showing sqlserv using 32 gig? Any ideas?

    Thanks

  • March 15, 2014 at 5:47 am

    #1697405

    It is depend on system file installation. if you have installed windows on 32-bit platform, SQL consume max 32 GB.

    you have to install Windows and SQL server both on 64 bit platform.

    i sure, it will help you.

  • March 15, 2014 at 8:22 am

    #1697416

    kshaileshbca (3/15/2014)

    if you have installed windows on 32-bit platform, SQL consume max 32 GB.

    You might want to check your facts....

    The memory limit on 32 bit is, in fact 2GB by default. 3GB with the /3GB switch and well above 32 GB with the /PAE switch and AWE enabled

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • March 15, 2014 at 8:25 am

    #1697417

    TST, hard to say anything definitive without a lot more data, but if SQL doesn't need more than 32GB it won't necessarily allocate more.

    Check that nothing else on the server is consuming a lot of memory. Make sure you don't have large pages enabled. If it's a VM, check what the reserved memory is for that guest.

    Are there signs of memory pressure? Is SQL under any load?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • March 16, 2014 at 9:26 am

    #1697487

    First thing I would look at is Windows able to see all the memory.

    If Windows cannot see the 64GB, neither will SQL server.

    Not all versions can see 64GB, and Numa architecture actual memory configuration can be a factor.

    I had a 2 proc machine, we took one proc out for licensing, and needed to fill certain slots that the one proc could see.

    You could override this in the BIOS, but not as efficient.

    Then as Gail mentioned, SQL will not use the full allocation unless it needs to.

    So you would have to check for signs of memory pressure.

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

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