Are there known issues with using AWE to access > 4Gb RAM with SQL 2000?

  • Are there known issues with using AWE to access > 4Gb RAM with SQL 2000?

    Does using AWE introduce a significant extra CPU load to your server?

    I ask because we recently went from 4Gb to 8Gb of RAM on the physical server (and from 3Gb to 6Gb for SQL) and had an issue where the CPU usage jumped from it's normal 40% usage to almost 80%.

    We had installed some system software the day before this occurred (about 10 days after we did the SQL memory upgrade) and we removed it and rebooted the server and everything went back to normal.

    I hope this was caused by the system software problem rather than any potential problem with AWE and SQL. I have read individual articles about problems with AWE and > 4Gb RAM.

    Is there a collected list of know AWE and SQL issues somewhere?

    Tom.

  • If you have SP4 installed you need a hotfix

    http://support.microsoft.com/default.aspx?kbid=899761

     


    * Noel

  • I run 32gb ram using awe with no problems. I saw cpu drop significantly. 

    As mentioned if you have sp4 applied you must have a fix applied

    SQL2000-KB899761-v8.00.2040-x86x64-ENU.exe

    which fixes a problem whereby only half the awe becomes available.

    [font="Comic Sans MS"]The GrumpyOldDBA[/font]
    www.grumpyolddba.co.uk
    http://sqlblogcasts.com/blogs/grumpyolddba/

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

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