INTRODUCTION
Microsoft SQL Server 2000 hotfixes are created for specific SQL Server service packs. For example, you cannot apply a hotfix that was designed for SQL Server 2000 Service Pack 3 (SP3) to an installation of SQL Server 2000 SP4 unless a special case is noted for that hotfix. You must apply a SQL Server 2000 SP3 hotfix to an installation of SQL Server 2000 SP3. You must apply a SQL Server 2000 SP4 hotfix to an installation of SQL Server 2000 SP4.
By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack. For example, the SQL Server 2000 SP3 hotfixes are included in SQL Server 2000 SP4.
However, there are two special cases where a hotfix is not included in the next SQL Server service pack:
- The hotfix was released after the next service pack was locked down for Beta testing:
For Beta testing to be effective, the testing must cover most of the changes that will be included in the product. Therefore, at some time, we have to decide what will be included in the final version of a service pack. We must lock down the contents so that we can create the Beta version that customers will test. After the service pack has been locked down, only critical changes may be added to the lock-down version of the service pack.
- The hotfix was released after the next service pack was released:
After any service pack is burned to CD and released, we cannot change that service pack.
The lock-down build of SQL Server 2000 SP3 hotfixes that is included in SQL Server 2000 SP4 is build 8.00.0996.
For more information about which SQL Server 2000 SP3 hotfixes are included in SQL Server 2000 SP4, click the following article number to view the article in the Microsoft Knowledge Base:
810185
SQL Server 2000 hotfix update for SQL Server 2000 Service Pack 3 and 3a
Any SQL Server 2000 SP3 hotfix that was included in build 8.00.0996 or in an earlier build is included in SQL Server 2000 SP4. By default, any SQL Server 2000 SP3 hotfix that was included in build 8.00.1000 or in a later build is not included in SQL Server 2000 SP4.
This cumulative hotfix package contains the SQL Server 2000 SP3 hotfixes that roughly correspond to build 8.00.1009 through build 8.00.1031, inclusive. Therefore, any SQL Server 2000 SP3 hotfix that was included in that range of builds is included in SQL Server 2000 SP4 build 8.00.2187. This build is also known as build 2187.
Important notes- You may have to restart the computer after you apply this cumulative hotfix package.
- If you are currently running a SQL Server 2000 SP3 build from build 8.00.1009 through build 8.00.1031, test SQL Server 2000 SP4 before you upgrade. You can also upgrade to SQL Server 2000 SP4, and then immediately install this cumulative hotfix package.
- If you are running a SQL Server 2000 SP3 build that is later than build 8.00.1031, you may require a later hotfix than this package contains.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
894905
Cumulative list of the hotfixes that are available for SQL Server 2000 SP4
- SQL Server 2000 SP3 hotfixes that were included in build 8.00.1032 and in later builds are included in later SQL Server 2000 SP4 builds.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
894905
Cumulative list of the hotfixes that are available for SQL Server 2000 SP4
- No hotfixes for SQL Server 2000 Analysis Services are included in this cumulative hotfix package.
For more information about a cumulative hotfix package for SQL Server 2000 Analysis Services, click the following article number to view the article in the Microsoft Knowledge Base:
907323
Hotfix rollup package for SQL Server 2000 Analysis Services Service Pack - Build 2174
- If you attempt to install or to uninstall this hotfix package on a 32-bit cluster, the hotfix package is not installed or uninstalled on the remote node. You must install or uninstall the hotfix package directly on the node.
- This article and package replaces the previously released cumulative hotfix package that is described in the following Microsoft Knowledge Base article:
904660 A cumulative hotfix package is available for SQL Server 2000 Service Pack 4 build 2162
MORE INFORMATION
How to obtain the cumulative hotfix package
To obtain the cumulative hotfix package for x86-based operating systems and for x64-based operating systems, visit the following Microsoft Download Center Web site:
To obtain the cumulative hotfix package for Itanium-based operating systems, visit the following Microsoft Download Center Web site:
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
SQL Server 2000 post-SP3 hotfixes that are included in SQL Server 2000 post-SP4 build 8.00.2187
900625 FIX: The error message that the SELECT statement returns may contain user data in SQL Server 2000
893172 FIX: An access violation may occur when you use the READPAST lock hint and you use a non-clustered index in your query in SQL Server 2000
892923 FIX: Differential database backups may not contain database changes in the Page Free Space (PFS) pages in SQL Server 2000
891585 FIX: Database recovery does not occur, or a user database is marked as suspect in SQL Server 2000
891268 FIX: You receive a 17883 error message and SQL Server 2000 may stop responding to other requests when you perform large in-memory sort operations
891201 FIX: Performance is significantly reduced when you set trace flag 9134 to prevent error message 601 in SQL Server 2000
891017 FIX: SQL Server 2000 may stop responding to other requests when you perform a large deallocation operation
892935 FIX: You experience slow performance when you join local partitioned views with a table in SQL Server 2000
892840 FIX: 17883 errors may be written to the SQL Server error log when you run a query that generates many floating point exception errors in SQL Server 2000
894257 FIX: You receive an "Incorrect syntax near ')'" error message when you run a script that was generated by SQL-DMO for an Operator object in SQL Server 2000
897572 FIX: You may receive a memory-related error message when you repeatedly create and destroy an out-of-process COM object within the same batch or stored procedure in SQL Server 2000
896985 FIX: The Subscriber may not be able to upload changes to the Publisher when you incrementally add an article to a publication in SQL Server 2000 SP3
887700 FIX: Server Network Utility may display incorrect protocol properties in SQL Server 2000
897578 FIX: Only the master database and the tempdb database are listed when you try to create a new job in SQL Server Enterprise Manager
892551 FIX: You receive a SqlException error message when you call the sp_addmergepublication stored procedure when the Active Directory directory service is not available in SQL Server 2000
892392 FIX: Query performance may be slower if the query contains both a GROUP BY clause and a DISTINCT keyword on the same column
892205 FIX: You may receive a 17883 error message when SQL Server 2000 performs a very large hash operation
892940 FIX: You experience delays and receive a 17883 error message when SQL Server 2000 performs a large and complex query plan that uses hash operators
894254 FIX: A complex query that includes a UNION ALL operator and an EXISTS clause may fail in SQL Server 2000
891866 FIX: The query runs slower than you expected when you try to parse a query in SQL Server 2000
892985 FIX: You may experience unexpected delays in query execution and unexpected time-out situations, and you may receive error message 17883 when you use the BULK INSERT command in SQL Server 2000
896425 FIX: The BULK INSERT statement silently skips insert attempts when the data value is NULL and the column is defined as NOT NULL for INT, SMALLINT, and BIGINT data types in SQL Server 2000
896980 FIX: The query plan may take longer than expected to compile, and you may receive error message 701, error message 8623, or error message 8651 in SQL Server 2000
898115 FIX: The subquery in a CASE function is evaluated even if the condition in the WHEN expression is false in SQL Server 2000
902851 FIX: SQL Server 2000 may intermittently appear to stop responding (hang) during a scheduled maintenance DBCC DBREINDEX operation
892310 FIX: The results are different every time that you run a complex query that contains a hash outer join operator in SQL Server 2000
895187 FIX: You receive an error message when you try to delete records by running a Delete Transact-SQL statement in SQL Server 2000
900335 FIX: The SQL Server 2000 automatic database recovery operation may not succeed if an index contains a FLOAT data type or a REAL data type, and this data type contains a NaN value
902852 FIX: Error message when you run an UPDATE statement that uses two JOIN hints to update a table in SQL Server 2000: "Internal SQL Server error"
911678 FIX: No rows may be returned, and you may receive an error message when you try to import SQL Profiler trace files into tables by using the fn_trace_gettable function in SQL Server 2000
909089 FIX: An access violation may occur when you try to run a Transact-SQL query in SQL Server 2000
909369 FIX: Automatic checkpoints on some SQL Server 2000 databases do not run as expected
909380 FIX: Error message 17883 may be logged in the error log when you try to manually update table statistics in SQL Server 2000
909734 FIX: An error message is logged, and new diagnostics do not capture the thread stack when the SQL Server User Mode Scheduler (UMS) experiences a nonyielding thread in SQL Server 2000 Service Pack 4
910392 FIX: You may receive incorrect results when you run a Transact-SQL query in SQL Server 2000
910707 FIX: When you query a view that was created by using the VIEW_METADATA option, an access violation may occur in SQL Server 2000
910895 FIX: You may receive an error message when you set the database collation to Thai_CI_AS and you try to run a Transact-SQL update query in SQL Server 2000
900416 FIX: A 17883 error may occur you run a query that uses a hash join in SQL Server 2000
910392 FIX: You may receive incorrect results when you run a Transact-SQL query in SQL Server 2000
901200 FIX: You may receive a "Server: Msg 7358, Level 16, State 1, Line 1" error message after you run a linked server query in SQL Server 2000 Service Pack 4
905765 FIX: A view is corrupted after you run the DBCC DBREINDEX Transact-SQL statement to rebuild the clustered index on a view in SQL Server 2000
908156 FIX: You receive an error message when MS DTC for SQL Server 2000 reuses a server process identifier (SPID) to enlist in a distributed transaction
910710 FIX: You receive an error message when a Visual Basic application opens a dynamic cursor on a GROUP BY query in SQL Server 2000 Service Pack 4
911677 FIX: A query may run more slowly against SQL Server 2000 post-SP3 hotfix build 8.00.0988 than a query that you run against SQL Server 2000 post-SP3 hotfix builds that are earlier than build 8.00.0988
913684 FIX: You may receive error messages when you use linked servers in SQL Server 2000 on a 64-bit Itanium processor
914298 FIX: You may receive an error message, and the SQL Server process may crash when you copy or transfer SQL Server 2000 data
836651 FIX: You receive query results that were not expected when you use both ANSI joins and non-ANSI joins
898709 FIX: Error message when you use SQL Server 2000: "Time out occurred while waiting for buffer latch type 3"
911569 FIX: You may receive an access violation error message when you run a linked server query that includes a subquery
914384 FIX: The database status changes to Suspect when you perform a bulk copy in a transaction and then roll back the transaction in SQL Server 2000
909100 FIX: The performance of the statement that raises an error differs from the performance of the statement that does not raise an error when you trace exception events in SQL Server 2000 on an IA-64 computer
909379 FIX: You receive a 17883 error message when you run a complex query against SQL Server 2000
913991 FIX: Hotfix files may not be copied to remote nodes when you install a 32-bit hotfix, and hotfix files may not be removed from remote nodes on a computer that is running SQL Server 2000 in an MSCS environment