SQL 2000 EE AWE Problem

  • Hi all

    I've read the following to articles regarding this subject but still not sure if I've understood/implemented AWE correctly:

    http://support.microsoft.com/kb/274750

    http://www.sql-server-performance.com/articles/per/awe_memory_sql2000_p1.aspx

    Server Config:

    Windows 2000 Server Std Edition SP4

    SQL Server 2000 Enterprise Edition SP4

    4GB Ram - was 2GB, just added another 2GB

    I'm trying to limit SQL Server to 3GB but not been very successful.

    AWE Enabled = 1 via sp_configure

    max memory = 3072 ie 3GB

    However in performance monitor, the Total Memory is only 1.6GB and the same in Task Manager?

    I downloaded and installed a hot fix where only 50% of the memory was being used once AWE was activated but still no change.

    http://support.microsoft.com/kb/899761

    I've re-read both articles and it seems that I shouldn't enable AWE and that I can't actually limit to 3GB?

    If I'm understanding this correctly, SQL can only use all the memory (4GB) and AWE isn't required?

    The articles also mention that I can't use the /3GB switch because the OS is std

    I'm really confused

    Thx


    John Mac Pherson
    Database Administrator
    Optimal Information Systems Pty (Ltd)
    jmacpherson@ois.co.za

  • John,

    Apparently your server config does only allows you to use the memory up to 2GB for the SQL.

    AWE should not and will need not to be enabled for any server less than 4GB. Apps only use AWE to access >3GB memory.

    Assuming you've got a server with 4GB memory, here's what happening

    1. Default, kernel (OS) = 2GB and user-mode = 2GB

    2. If you add /3GB in boot.ini and reboot server, kernel = 1GB and user-mode = 3GB

    3. But you'll always miss ~300MB memory. I.e. you can only see 2.7GB memory being used by SQL because the "missing" (which is not really missing, but just not being seen) is the MemToLeave area where it handles/contains pages >=8k.

    Therefore, in you case, SQL showing memory usage of ~1.6GB is correct. Have a read at the paragraph below and it says on Windows 2K server, the user-mode memory is still only 2GB although you've upgraded your server to 4GB. The /3GB isnt supported by your windows. You'l either have to upgrade it to Windows 2003 and add the /3GB switch, then you'll get ~2.7GB memory usage by your SQL.

    Simon

    http://support.microsoft.com/kb/291988/

    When the /3GB switch is used with Windows 2000 Professional or with Windows 2000 Server, the kernel components are loaded into the memory space by using the 4 GB RAM Tuning feature in the same way as they load in Windows 2000 Advanced Server and in Windows 2000 Datacenter Server. This functionality lets device-driver developers test their drivers in this configuration without having to install Windows 2000 Advanced Server or Windows 2000 Datacenter Server. The user-mode memory space is still limited to 2 GB.

    Simon Liew
    Microsoft Certified Master: SQL Server 2008

  • Simon may be a rookie in this forum, but he has given a comprehensive and correct answer to the problem.

    Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.

    When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara

  • Simon, thanks for answering and providing the clarification I was looking for.

    Thx


    John Mac Pherson
    Database Administrator
    Optimal Information Systems Pty (Ltd)
    jmacpherson@ois.co.za

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

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