sql server 2005 memrry on 32 bit systems

  • Hi All,

    Can anyone share their expericences which one is good and bad about below configurations on 32 bit systems and sql server 2005.

    On what factors we can choose either of the below and which one would be a best match based on the scenario whether it is MTL or Bpool pressure?

    Also, would like to know how much memory can i make use of below physical RAM if it is 64 gigs or 32 gigs.

    Environment

    Windows 2003 32 bit

    SQL server 2005 sp4 32 bit

    64 GB Physical RAM

    1. /3GB + AWE

    2. /PAE + AWE

    3. /PAE + /3GB + AWE

    Looking forward for lot of answers....

    Thanks in advance.

  • Oracle_91 (1/10/2013)


    Hi All,

    Can anyone share their expericences which one is good and bad about below configurations on 32 bit systems and sql server 2005.

    On what factors we can choose either of the below and which one would be a best match based on the scenario whether it is MTL or Bpool pressure?

    Also, would like to know how much memory can i make use of below physical RAM if it is 64 gigs or 32 gigs.

    Environment

    Windows 2003 32 bit

    SQL server 2005 sp4 32 bit

    64 GB Physical RAM

    1. /3GB + AWE

    2. /PAE + AWE

    3. /PAE + /3GB + AWE

    Looking forward for lot of answers....

    Thanks in advance.

    Use option 2 if you have 64 GB of RAM. It will allow you to access all 64 GB. Make sure you set the max memory option using sp_configure to something sensible to allow the OS some memory to do its work, else SQL Server will try to consume all memory.

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

  • Oracle_91 (1/10/2013)


    1. /3GB + AWE

    This would allow SQL to use no more than 3GB of memory, as enabling AWE required the PAE switch to be on

    3. /PAE + /3GB + AWE

    This option would allow no more than 16 GB of memory to be used and would risk OS instability and fun memory errors (lack of available page table entries)

    /3GB is fine with just 4 GB of memory, OK with 8, risky with 16 and silly with anything above that.

    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
  • Hi,

    Thanks for sharing your thoughts.

    Gila, I have a question, how does the calucation comes to 16Gigs If I have to choose /PAE + /3GB + AWE ?

    Thank you.

  • From Books Online:

    If there is more than 16 GB of physical memory available on a computer, the operating system requires 2 GB of virtual address space for system purposes and therefore can support only a 2 GB user mode virtual address space. For the operating system to use the memory range above 16 GB, be sure that the /3gb parameter is not in the Boot.ini file. If it is, the operating system cannot use any physical memory above 16 GB.

    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 5 posts - 1 through 4 (of 4 total)

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