Post reply

SQL 2008 AWE

  • June 20, 2013 at 10:01 am

    #294894

    Greetings.

    I am dealing with a SQL 2008 (non R2) 32 bit installation on a 64 bit OS with 32GB of RAM.

    We had some major issues happening on the server, and when I investigated, I saw the dreaded "Failed Virtual Allocate Bytes: FAIL_VIRTUAL_RESERVE 589824" message.

    The "Maximum server memory" setting is set extremely high, higher than the available RAM on the machine.

    I have 2 questions:

    1. Will the 32 bit version of SQL Server still try to allocate memory over the 4 GB limit even though it's a 32 bit process?

    2. Will enabling AWE help this problem, and if so are there any risks to enabling it?

    Thanks in advance.

  • June 20, 2013 at 10:05 am

    #1626006

    Jeremy-475548 (6/20/2013)

    1. Will the 32 bit version of SQL Server still try to allocate memory over the 4 GB limit even though it's a 32 bit process?

    Not without AWE enabled, even with it, only the data cache can use memory over 4GB

    2. Will enabling AWE help this problem, and if so are there any risks to enabling it?

    AWE won't help a failed FAIL_VIRTUAL_RESERVE. Try increasing the value for the -g parameter a little, if the problem persists consider upgrading to 64-bit SQL Server.

    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

Viewing 2 posts - 1 through 1 (of 1 total)

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