Microsoft distributes Microsoft SQL Server 2000 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release.
This article describes the following about this hotfix release:
The issues that are fixed by this hotfix package
The prerequisites for installing the hotfix package
Whether you must restart the computer after you install the hotfix package
Whether the hotfix package is replaced by any other hotfix package
Whether you must make any registry changes
The files that are contained in the hotfix package
If Address Windowing Extentions (AWE) support is enabled, a single instance of SQL Server 2000 can only use a maximum of 50 percent of the physical memory that is on the computer.
Note This problem only occurs on 32-bit versions of Microsoft SQL Server 2000 Service Pack 4 that are running on either an x86-based computer or on an x64-based computer.
For example, if you have a computer that has 16 GB of RAM and AWE is enabled, a single instance of SQL Server 2000 can only access 8 GB of RAM.
To determine whether AWE is enabled, run the following script from SQL Query Analyzer:
If run_value is set to 1, AWE is enabled on the server.
To view the behavior, examine the SQL Server: Memory Manager/Total Server Memory (KB) counter in System Monitor. On a computer that is running SQL Server Service Pack 3 (SP3), this value may be up to the amount of physical memory that is on the computer. On a computer that is running SQL Server SP4, this value will never be more than 50 percent of the physical memory.
This behavior only occurs on computers that have more than 2 GB of RAM.
If you use AWE memory and you have set the value of the max server memory option to less than 50 percent of physical memory, you will not be affected by this bug.
AWE is not available on all versions of SQL Server 2000. For example, AWE is not available for MSDE, SQL Server 2000 Standard Edition, SQL Server 2000 Personal edition, or installations of only the SQL Server 2000 Tools.
If you are running SQL Server 2000 SP4 on an IA-64-bit system, you will not be affected by this bug.
This behavior occurs because the total number of usable buffer pages was based on an incorrect comparison of the number of SQL pages (8 KB) and system pages (4 KB). The problem does not occur on IA-64-bit systems because the code that makes this comparison is not executed.
To obtain this hotfix, visit the following Microsoft Web site:
You do not have to restart the computer after you apply this hotfix.
You do not have to change the registry.
Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.
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 item in Control Panel.
SQL Server 2000 32-bit versions for x86-based computers
Date Time Version Size File name ----------------------------------------------------------- 14-May-2005 01:11 2000.80.2040.0 9,150,464 Sqlservr.exe
SQL Server 2000 32-bit versions for x64-based computers
Date Time Version Size File name Platform --------------------------------------------------------------------- 14-May-2005 01:11 2000.80.2040.0 9,150,464 Sqlservr.exe x86
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.
For more information about AWE, click the following article number to view the article in the Microsoft Knowledge Base:
274750 How to configure SQL Server to use more than 2 GB of physical memory
For more information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages
For more information about the terminology that Microsoft uses when it corrects software after it is released, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates