Article ID: 330391 - View products that this article applies to.
This article was previously published under Q330391
The information in this article applies to Microsoft SQL Server 2000 Service Pack 3 (SP3) hotfix builds 761 through 977 on all operating systems. The information in this article also applies to SQL Server 2000 SP3 hotfix builds 977 through 2037 when they are installed only on a computer that is running Microsoft Windows 98, Microsoft Windows Millennium Edition, or Microsoft Windows NT. If you are trying to install SQL Server 2000 SP3 hotfix build 977 or a later build on a computer that is running Microsoft Windows 2000, Microsoft Windows XP, or Microsoft Windows Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:
842960SQL Server 2000 Service Pack 4 (SP4) and later versions are not supported in Windows 98, in Windows Millennium Edition, or in Windows NT. Therefore, there is no hotfix support for those operating systems in SQL Server 2000 SP4 and in later versions.
(http://support.microsoft.com/kb/842960/ )Description of the 32-bit SQL Server 7.0 and SQL Server 2000 hotfix installer
Microsoft SQL Server 2000 hotfixes will be packaged and delivered to users as a self-extracting executable file. The hotfix installer helps you install hotfixes by using a GUI-based Setup program. By using the hotfix installer, you can also automate the hotfix installation process across your whole organization.
The name of the hotfix installer executable file will have this format:
If you experience disk space errors when you extract the package, see the following article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/301913/ )BUG: Error message "There is not enough space on drive" occurs when you extract SQL Server 2000 dowloads
Before you install the hotfix installerBefore you install the hotfix installer, Microsoft recommends that you perform a backup of these databases:
How to use the hotfix installerTo start the hotfix installation process, you must run the hotfix executable file. For a standard hotfix installation, you must save and run the hotfix executable file on the server computer. For instructions about how to install hotfixes on a cluster installation, read the "Cluster installation" section of this article. To run the installation, you must log on to the operating system with a user account that has local administrative credentials.
When you run the installation, the package files are extracted to the temp folder. Then, a GUI-based hotfix installer tool starts that guides you through the rest of the installation process.
What files are updated by this hotfix?A list of files that are updated by this hotfix is located in an INF file. You must run the hotfix executable file and extract the INF file to review the file list.
To obtain a list of the files that the hotfix updates, follow these steps:
1. Start the hotfix executable file. Run the program until you are the extraction page. The files are then extracted to the %TEMP% folder. Do not cancel the setup yet. If you cancel the setup, all the extracted files are removed from the %TEMP% folder.
2. After you see the Welcome screen for the hotfix installer, locate the %TEMP% folder. Use the timestamp on the folders that are in the TEMP folder to identify a folder named pftXX~tmp, where XX is a random number
3. Locate the Hotfix.inf file in this folder to obtain a complete file list from the [FILES] section of this INF file. Additionally, you can also review the [SCRIPTS] section of the Hotfix.inf file to find out if the update runs any scripts against your SQL Server installation.
4. Now, you can cancel the setup to remove the temporary folder.
Note You can also obtain the list of the files that the hotfix updates by reviewing the Microsoft Knowledge Base article that was authored for this hotfix. The article number is shown in the initial Welcome screen of the hotfix installer.
How the installer worksThe hotfix installer uses these steps to complete the installation:
SQL Server 2000 cluster installationsTo apply the hotfix package to a clustered SQL 2000 installation, you must run the hotfix package on the node that owns the SQL Server resource. Then, the hotfix installer will take the SQL Server resource offline and update the binaries on all nodes of the cluster. Finally, the SQL Server Resource is brought online, and the installer runs any install scripts (.sql) that were shipped as part of the hotfix.
SQL Server 7.0 cluster installationsFor clustered SQL Server 7.0 installations, you must first uncluster SQL Server by running the SQL Server Failover Wizard from the primary cluster node of each virtual SQL Server.
Active/ActiveFollow these steps for an Active/Active installation:
Active/PassiveFollow these steps for an Active/Passive installation:
Command line parametersHere is a list of the command line parameters that are available with this hotfix package.
Note You can use the start /wait standard Windows command line prefix in front of the command to return control to the command prompt after the hotfix installer completes.
Option Definition ------ ---------- /s Disable Self Extraction progress dialog. Must come before /a. /a This parameter must come before all parameters except /s if you are running the hotfix by using the self-extracting EXE, and you want to include parameters for unattended installations. This is a mandatory parameter for the installer to run in the unattended mode. /q This flag causes the Setup program to run in silent mode with no user interface. /allinstances This is an SQL specific key that patches all instances of SQL Server in silent mode that pass the applicability rules. This flag can also be used to patch all SQL Server virtual servers that pass the applicability rules and needs to be run from the active node. INSTANCENAME Name of the instance of SQL Server. You must enter it as INSTANCENAME=yourinstancename BLANKSAPWD Means blank sa password for SQL Authentication. If you enter this parameter on computers that are running Microsoft Windows NT or Microsoft Windows 2000, the default Windows Authentication logon is overridden and it tries to log on with a blank sa password. The correct format for this parameter is BLANKSAPWD=1. This parameter is recognized only for unattended installations. SAPWD Non-blank sa password. If you enter this parameter, it must be in the form of SAPWD=yoursapassword. This parameter overrides default Windows Authentication on computers that are running Windows NT or Windows 2000, or a BLANKSAPWD, if entered.
Command line examples
How to perform an unattended installationAn unattended installation is similar to the interactive installation described earlier. For a silent installation, you must execute the self-extracting EXE with the /q parameter. If you are applying the hotfix to a named instance, you must specify the instance name on the command line by using the INSTANCENAME parameter. If the selected instance qualifies for the hotfix, the installer will apply the patch, as described earlier. If the INSTANCENAME parameter is not supplied, the hotfix uses the default instance for SQL Server.
For unattended installations on a cluster, you can use the same syntax like in a noncluster scenario. For example, if you have a named instance in a cluster named HELLO\Inst1, where HELLO is the Virtual Server name, the syntax is similar to:
Log fileEvery action that is performed by the hotfix installation process is recorded in the setup log file. The log file will have enough information about each action taken at each stage of the installation, and the specific operation performed on each file. The hotfix saves the log file in the %WINDIR%\SQLHotfix folder. For each log file, the program creates a unique name:
The question mark (?) is how many times you tried to install the hotfix on the computer.
For a successful installation, at the end of the log file you will see this message: Similarly this message means a failure has occurred during the hotfix installation: This message indicates that the installation was canceled in the middle of the setup process, and the installation was aborted: For failed installations, a corresponding error code is written to the hotfix installer log.
How to remove or rollback the hotfixIf you decide to rollback a hotfix package, you must use a manual process to remove the updated files. A complete list of the files and the appropriate backup directories that were created by the hotfix is listed in the setup log file. As mentioned earlier, the installer backs up the current files to the backup folder structure (documented earlier in this article) before replacing them with the new files. To rollback the hotfix, you must stop all services and replace all the files from the backup folder specified in the log file. If the hotfix did run any scripts during installation, there is no quick automatic way to roll back the changes it made to the system databases. That is why it is important for you to back up the system databases before you apply the hotfix.
If you must rollback from this hotfix, and your setup log file (or the INF file) indicates that the hotfix did run one, or more, .sql scripts against your server, you must follow these steps:.
Important The following steps involve rebuilding your master database and restoring it from a master backup that was taken before you applied the hotfix. If you created any new user databases after you applied the hotfix, you must backup these user databases now so that you can restore these databases, after completing the following steps:
Contact us for more help
Connect with Answer Desk for expert help.