- ReadmeSql2k32asp4.htm: "Service Pack 4 for Microsoft SQL Server 2000 - Analysis Services"
- ReadmeSql2k32sp4.htm: "Service Pack 4 for Microsoft SQL Server 2000 - Database Components"
- ReadmeSql2k32desksp4.htm: "Service Pack 4 for Microsoft SQL Server 2000 - Desktop Engine (MSDE 2000)"
- ReadmeSql2k64sp4.htm: "Service Pack 4 for Microsoft SQL Server 2000 (64-bit)"
Information that has changedThe following information has changed since publication of the SP4 readme files.
Running Address Windowing Extensions (AWE) with SQL Server 2000 SP4Important We have found an issue with the final build of SQL Server 2000 SP4 that affects customers who run SQL Server with AWE support enabled. This issue does not affect the Itanium-based computers or other components of SQL Server beyond the relational databases, such as SQL Server 2000 Analysis Services, SQL Server 2000 Reporting Services, and SQL Server 2000 Notification Services. This issue only affects computers that have more than 2 GB of memory where AWE has been enabled and where more than half of the total system memory is being allocated to a single instance of SQL Server. Customers who have this configuration should apply the hotfix in the following Microsoft Knowledge Base article after they upgrade to SQL Server 2000 SP4:
Hotfixes are not included in Service Pack 4Hotfixes 836651 and 826906 were not included in SP4. Customers who apply SP4 in addition to this hotfix will have the hotfix overwritten. A post-SP4 hotfix for these issues will be available shortly.
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
Smssql2ksp4.pdf fileSQL Server 2000 SP4 includes a Smssql2ksp4.pdf file. This file contains a reference to Sms2kdef.bat and Sql2kdef.iss. However, these files no longer exist in the SQL Server 2000 SP4 package.
Note Every time that you run an attended installation of Database Components, the setup options will be written to the Setup.iss file that is located in the \System folder. For more information, see the "unattended installation" section in the SQL Server 2000 SP4 readme file.
SQL Query AnalyzerSQL Query Analyzer will permit connections to SQL Server 2005. However, some functionality may not be available. This functionality includes the following:
- Server Trace: The Server Trace window will not display any data.
- Object Search: The object search will not work.
- Manage Statistics: Existing statistics will not be displayed in the Manage Statistics dialog box.
Registry extended stored proceduresChanges were made to extended stored procedures that access the registry. Only members of the system administrator server roles may freely use these extended stored procedures without any difference in behavior from earlier service packs. For example, when you run queries that call registry extended stored procedures, you may receive an “access is denied” error message.
Warning The registry extended stored procedures are undocumented. They are subject to change without notice. And they are not officially supported to be used by applications. Therefore, we do not recommend that you call these procedures in the client code. There is no guarantee that these procedures will be available in later versions of SQL Server.
If all the following conditions are true, see Microsoft Knowledge Base article 887165:
- You are using registry extended stored procedures.
- You are not a system administrator.
- You require that SQL Server behave the way that it did before you upgraded to SP4.
Upgrade SQL Server 2000 Desktop Engine (MSDE) to other versions of SQL Server 2000If you upgrade SQL Server 2000 Desktop Engine (MSDE) to a different version of SQL Server 2000, such as to Personal Edition or to Developer Edition, you must reinstall SQL Server 2000 SP4 after you upgrade MSDE.
Avoid errors when you connect to a third-party database by using Analysis ServicesIf you are running Analysis Services SP4 on an AMD 64 system, and you plan to connect to a third-party database, confirm that the connectivity components for that database are certified for use under WoW by the third-party vendor. If those components are not certified, you may experience errors.
Avoid errors when you try to obtain diagnostics for an instance of SP3If you are installing SP4 on a computer where you will also be running SQL Server 2000 SP3, copy the Dbghelp.dll file from the SP4 BINN folder, and then add the Dbghelp.dll file to the SP3 BINN folder. After you do this, you can successfully capture diagnostics for the instance of SP3 if you have to do this later.
Summary dialog box for SQL Server 2000 64-bit SP4 SetupAfter you have upgraded to SP4 on SQL Server 2000 64-bit, the summary dialog box may show the instance of SQL Server as "success." However, dependant components or features may show as "not selected." This is known behavior. For more information, see the SQL Server SP4 Setup log.
Add new features to SQL Server 2000 (64-bit)SQL Server 2000 64-bit SP4 may not correctly add features or may not correctly upgrade added features. This problem may occur if the correct Windows Installer file name or ProductCode was not in the command line or in the Setup.ini file when the feature was originally added. To resolve this problem, uninstall the newly added feature, and then reinstall it by using the correct Windows Installer file name or ProductCode.
Note Although a feature has been added incorrectly, it may still appear in the Add or Remove Programs tool in Control Panel.
Upgrade from SQL Server 2000 64-bit SP4 Beta to the Release to Manufacturing (RTM) versionYou must uninstall SQL Server 2000 64-bit SP4 Beta before you install the RTM version.
Uninstall a SQL Server 2000 64-bit SP4 clusterTo uninstall a SQL Server 2000 64-bit cluster, you will have to use the Unattended Setup feature and a corresponding Template.ini file. This Template.ini file should contain settings for the SQL Server 2000 64-bit installation. For more information about Template.ini files, see SQL Server 2000 64-bit Books Online.
64-bit Analysis Services installationIf Analysis Services 64-bit is not installed as part of an initial configuration, you cannot add Analysis Services through instance maintenance. If you want to add Analysis Services after the Setup process is completed, you will have to install Analysis Services as a component of a new, additional instance.
64-bit maintenance modeDuring maintenance mode, adding 64-bit Analysis Services features to an existing 64-bit SQL Server feature, or trying to add a 64-bit SQL Server feature to an existing 64-bit Analysis Services feature instance is not supported.
Items that are not documented correctly in the Database Components SP4 readme file
3.5 Install database components on replicated serversSection 3.5 of the Database Components SP4 readme file (ReadmeSql2k32sp4.htm) incorrectly refers to "an instance of MSDE 2000." Instead, it should refer to "an instance of the database engine."
Section 3.5 of the Database Components SP4 readme file also states the following:
3.4 Install on a failover clusterSection 3.4 of the 64-bit SP4 readme file (ReadmeSql2k64sp4.htm) currently states the following:
- Rebuild the node in the failover cluster. For more information about rebuilding a node, see "How to recover from failover cluster failure in Scenario 1" in SQL Server 2000 Books Online.
- Run the original SQL Server 2000 Setup program to add the node back to the failover cluster.
- Run the SQL Server 2000 SP4 Setup program on the active node that is running virtual server.
- If you run the SQL Server 2000 SP4 Setup program from the node that is running virtual server, you may have to reinstall SQL Server 2000 SP4 on all nodes. You may also have to run the database upgrade scripts again. This requirement may be a problem if the instance of SQL Server on the existing nodes has a post-SP4 hotfix installed.
- You can perform a binary-only installation by running the SQL Server 2000 SP4 Setup program on the new node if the node is a passive node. A binary-only installation only updates the binaries on the node on which you run the SQL Server 2000 SP4 Setup program. A binary-only installation does run the database upgrade scripts. If you want to perform a binary-only installation, we recommend that you perform the installation on a test server before you implement the installation on a production server.