Post reply

Memory Upgrade Issue

  • June 7, 2005 at 9:52 am

    #88647

    Hi,
     
       We have following configuration:
     
    SQL SErver 2000 Enterprise Edition running on Win2k Advanced Server with Active/Passive Cluster Configuration
    Ram: 2 GB on Each node
     
    We upgraded memory on primary node to 4GB and left 2GB on Secondary node. And I have not enabled AWE on Sql server.  And left "Dynamically Configure SQL SErver memory" Configuration settings on. But memory usage is not increased on Primary node when i see it in Task manager. Do i need to change any configuration to affect memory upgrade i did on primary node. Any help greatly appreciated!
     
    Thank you in advance,
    Nari Patel
     


    Nari

  • June 7, 2005 at 10:00 am

    #563593

    If you don't add the /3GB switch to boot.ini, SQLServer will grab 2GB and the OS will grab 2. Since you went from 2GB to 4Gb, you should now be seeing more utilization of memory by SQL Server (since it can grab that whole 2GB now, instead of sharing it with the OS). Look into the /3Gb switch, PAE, and AWE for more information. In Books Online, check out Managing AWE Memory, Using AWE Memory on Windows 2000. I think there are a couple of good articles on this site regarding them as well.

  • June 7, 2005 at 10:07 am

    #563596

    Nari,

    You should use the /3GB switch in the primary node's boot.ini file. (Only the primary node, as the other hasn't been upgraded.)

    This will change the standard mapping of 2GB kernel/2GB user processes to 1GB kernel/3GB user processes. This will allow your SQL Server to address up to 3GB of memory.

    For more information, check out this MS Knowledge Base article:

    274750: How to configure memory for more than 2 GB in SQL Server  

    -- J.Kozloski, MCDBA, MCITP

  • June 7, 2005 at 10:13 am

    #563598

    It works.
     
    Thank you very much.


    Nari

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

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