SQL Server Performance

Memory with Standard Edition and x64 bit platform

Discussion in 'SQL Server 2005 Performance Tuning for DBAs' started by hooperdba, Nov 16, 2007.

  1. hooperdba New Member

    I'm new to x64 bit architecture.

    Server OS is 2003 R2 EE x64
    Sql is 2005 Std sp2 with hotfix
    4 way processors
    4 GB of RAM

    I reading that all x32 configurations do not apply... pae , awe
    enabled etc....

    after sp_configure ..sql is set to 2gb max memory setting.
    Does this not have to be increased for sql to see more
    memory .. I've confirmed that OS can see the 4GB but
    don't think SQL can.

    Does 'AWE enabled' still haveto be set up (or anything else)with this setup to optimize memory.

    thanks much
  2. jagblue New Member

    Hi John
    yes in 64 Platform their is no need to applt /3GB or /AWE flages
    But you can enable AWE and change Min server Memory to say 3 GB
    But you have to make sure that Lock Page in Memory option Enable for SQLServices Account
  3. Luis Martin Moderator

    Yes, after Fix 2040, you have to change AWE with sp_configuration and set the maximum memory do you want.
  4. hooperdba New Member

    so AWE must be turned on with sp_configure ?????
  5. satya Moderator

    Please be clear with your question and do not confuse with originator's question above, as it referred on X64 you don't need setting of AWE.
  6. thomas New Member

    Lock Pages In Memory privilege only works in Enterprise Edition, in Satandard edition it is ignored.
  7. merrillaldrich New Member

    I'm confused -- I have a server running a pure 64-bit setup: w2k3 standard edition 64-bit, SS 2005 standard edition 64-bit, 12GB RAM, and SQL Server sees and uses all the memory on the box just fine. What's the need for AWE in this situation? Why turn it on?
    Just curious...

  8. hooperdba New Member

    Did you set your max memory with sp_configure and if so to what min/max

Share This Page