This article was previously published under Q332004
This article has been archived. It is offered "as is" and will no longer be updated.
If you run SQL Server on multiprocessor computers with Address Windowing Extensions (AWE) enabled, the CPU may not be fully used and SQL Server scalability may be limited under extreme load conditions.
Service pack information
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 How to obtain the latest SQL Server 2000 service pack
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.
AWE memory permits applications to use more memory than is available through standard addressing by dynamically mapping the views of the non-paged memory to the standard address space. SQL Server was unmapping hot pages, causing page contention on "hot" pages that are unmapped. SQL Server was also pushing higher mapping activities than expected. You can use the AWE counters to monitor Microsoft Windows 2000 AWE activity in SQL Server.
For more information about AWE, see the "Using AWE Memory on Windows 2000" and "awe enabled Option" topics in the SQL Server 2000 Books Online.