Performance and Memory issues on Sql 2000 running Windows 2003 Enterprise R2

Posted on 2009-02-17
Last Modified: 2012-05-06

We upgraded to new hardware this weekend and a new OS on our Sql server Database system.  We moved from Windows 2000 running Sql Server 2000 databases and moved to WIndows 2003 Enterprise 2003 R2 running Sql Server 2000 and named the machine the same name and same IP address and ported the databases over to the new system.   We believe we could be having memory leaks or issues but not certain.

We are currently running on a IBM 3850 with a DS3300 for storage and our 3850 is configured as follows.

Windows 2003 Server Enterprise R2 at Sp2
Sql server 2000 at SP4
Boot ini switch we have 3GB and PAE enabled.
13.7 GB max memory for sql
16 GB Ram on server
paging = 48GB  
We also are running Trendmicro Officescan version 8 with exclusions.

Does anyone know of anything that we might be missing or have overlooked in this configuration or something else we might check.  

We have about 500 processes at any one time running on the system.

Thanks for your help

Question by:dtmhelp
    LVL 76

    Expert Comment

    You do not need the /3GB switch since you are not using AWE.
    Since you do not have Enterprise version of SQL, you can not use AWE.
    Check the advanced settings under properties of my computer, performance settings\advanced should be processor and memory priority for application rather than background services.
    You can also get the Server Performance adviser and run tests to see where your performance hit is.

    How big is your database?
    You can use perfmon to look at memory and processor performance to see whether the hit is coming from swapping memory (paging)

    Author Comment


    I forgot to add that we are using Sql Server 2000 Enterprise edition.

    Also the database is about 52 GB in size.

    LVL 76

    Accepted Solution


    Setup SQL to run with AWE. Note you should first double check that all the updates to your sql 2000 EE are applied including the hotfix dealing with AWE from the links below. Make sure the user used to run sql has lock pages in memory rights.
    Remove the /3GB from the boot.ini
    Hotfix SQL 2000 SP4 might be outdated:

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    How your wiki can always stay up-to-date

    Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
    - Increase transparency
    - Onboard new hires faster
    - Access from mobile/offline

    Microsoft has released remote PowerShell capabilities to all commercial Office 365 customers. So you can be controlled via PowerShell and not from the Office 365 admin center Download Windows PowerShell Module for Lync Online http://www.micros…
    The use of stolen credentials is a hot commodity this year allowing threat actors to move laterally within the network in order to avoid breach detection.
    In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
    Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…

    737 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    18 Experts available now in Live!

    Get 1:1 Help Now