SQL ????? ???????? ???????

???? ?????? ???? ??????
???? ID: 330391 - ?? ???????? ?? ?????? ??? ?? ?? ???? ???? ???? ??.
?? ???? ??? ?? ?? ??????? Microsoft SQL Server 2000 ?????? ??? 3 (SP3) ???????? builds ?? ??? ???????? ???????? ?? 977 761 ?? ???? ???? ??? ?? ???? ??? ?? ?? ??????? SQL Server 2000 SP3 ???????? ?? ?? ?? ??????? Microsoft Windows 98, Microsoft Windows Millennium ??????? ?? Microsoft Windows NT ??? ??? ???????? ?? ???? 2037 ?? ?????? ?? 977 ???? ?? ??? ?? ???? ????? ??? ?? ??????? ???? ????? ???, ?? SQL Server 2000 SP3 ???????? ?? 977 ????? ?? ???? ??? Microsoft Windows 2000, Microsoft Windows XP, ?? Microsoft Windows Server 2003 ??? ??? ???????? ?? ?????, ???? ?? Microsoft ???????? ??? ????? ?? ??? ????? ???? ?????? ?? ????? ????:
84296032-??? SQL Server 7.0 ?? SQL Server 2000 ???????? ???????? ?? ?????
SQL Server 2000 ?????? ??? 4 (SP4) ?? ??? ?? ??????? ??????? ???? ??? Windows 98 ???, Windows Millennium Edition ???, ?? Windows NT ???? ?????, ?? SQL Server 2000 SP4 ??? ?? ??? ?? ????????? ??? ?? ???????? ???????? ?? ??? ??? ???????? ???????
??? ?? ??????? ???? | ??? ?? ??????? ????

?? ????? ??

??????

Microsoft SQL Server 2000 ?????????? packaged ?? self-extracting ???????? ????? ????? ?? ??? ??? ?????? ???????????? ?? ??? ???? ?????? ???????? ???????? ???? GUI-?????? ????? ????????? ?? ????? ???? ?????????? ?? ??????? ???? ??? ???? ??? ???? ??? ???????? ??????? ?? ????? ??, ?????? ?? ?? ???? ??? ?? ???????? ???????? ??????? ????????? ?? ???? ???? ????? ?? ????

???????? ???????? ???????? ????? ????? ?? ??? ?? ?????? ????:

X.YY.ZZZZ_LangName.exe
  • X????? ??????? ?????? ?? ????? ???? ???
  • YY?? ??? ?? ??????? ?????? ?? ????? ???? ???
  • ZZZZ???????? ?????? ?? ????? ???? ???
  • LangName??? ????? ?? ??? ?? ???????? ???????? ???? ?? ??? abbreviation ???
?????? ?? ??? ???? ????????? ??????? ?? SQL Server 2000 ???????? ?????? 701 ?? ????:

8.00.0701_enu.exe.

??? ???? ????? ????? ????????? ?? ?? ????? ??????? ??? ????? ???? ?? Microsoft ???????? ??? ?????:
301913BUG: ?????? ????? ?? ?? SQL Server 2000 dowloads ??????? ???? ?? "????? ???????? ????? ???? ?? ?? ??????"

???? ???????

???????? ???????? ?? ??????? ???? ?? ????

???????? ???????? ??????? ???? ?? ???? Microsoft ??????? ???? ?? ?? ?? ??????? ?? ????? ?????:
  • ??????
  • msdb
  • ????
??? ???, ??? ???? ?????? ?????? ???? ?? ??? ????????, ???? ??? ?? ????? ???????????? ???? ?? ???? ?????? ????????? ?? ???? ??? ???? ??????? ????? ?? "???? ??????? ?? ?????? ????????" ?? ???? ?? ???? ???????? ???????? ?? ??????? ???? ?? ??? ?????????? ??????? ??? ?????? ???? ????? ??; ???????, ?? ?????? ??????? ??? ?????? ????? ?? ???? ???

???????? ??????? ?? ????? ???? ????

???????? ??????? ????????? ?? ??????? ???? ?? ??? ???? ???????? ???????? ????? ????? ????? ?????? ??? ???? ???? ???????? ??????? ?? ??? ?????? ?? ?? ?? ?????? ???? ?? ???????? ???????? ????? ????? ????? ???????? ?? ?????? ??? ??????? ??????? ?? ?????????? ?? ??????? ???? ?? ??? ???? ???? ?? ???? ??? ????????? ?? ??? ?? ???? ?? "??????? ???????" ??? ????? ??????? ?? ????? ?? ??? ???? ????? ??? ?? ???? ?? ??? ???????????? ????????????? ???? ??????? ?????????? ???? ?? ??? ???????? ???????

?? ?? ??????? ????? ???, ????? ??????? ?? ?????? ???temp???????. ??????? ?? ????, ?? ?? ???????? GUI-?????? ???????? ????? ?? ?? ??????? ????????? ?? ??? ??? ??? ???? ???????????

?? ???????? ?? ?????? ???-?? ?????? ?????? ?? ???? ????

?? ???????? ?? ?????? ?????? ?? ?? ??????? ?? ???? ?? INF ????? ??? ????? ??? ?? ???? ???? ?? ??????? ???? ?? ??? INF ????? ?? ??????? ?? ???????? ???????? ????? ????? ?? ????? ??????

???????? ?????? ?? ?? ??????? ?? ???? ?? ??????? ???? ?? ??? ????? ????? ?? ???? ????:

1. ???????? ???????? ????? ????? ?? ??????? ????? ?????? ???? ????? ???? ??? ?? ?? ????????? ?????? ??????? ?? % ?????? ??? ??? ???TEMP??????? % ??? ???? ????? ?? ???? ???? ??? ?? ????? ???? ???? % ?? ?????? ?? ??????? ????? ??? ???? ???TEMP??????? % ???

2. ?? after ???????????????????? ??????? ?? ??? ???????, % ?? ?????? ?????TEMP??????? % ??? ??????? ??? ??? ?? ?? ??????????? ?? ????? ????TEMP???? ?????? ?? ??????? ?? ??? ?????? ?? ??? pftXX~ tmp, ????XX????? ?????? ??

3. Hotfix.inf ????? ?? ?????? ????? ?? INF ?? [FILES] ??? ??? ?? ?? ????? ?? ????? ???? ??????? ???? ?? ??? ?? ??????? ??? ?????? ??? ??, ?? ?? ??? ???? hotfix.inf ?? [?????????] ??? ??? ?? ?????? ?? ??? ??? ?????? ???? ???? ?? ????????? SQL Server ???? ?? ??????? ????? ????????

4. ??, ?? ??????? ??????? ?? ??????? ?? ??? ????? ???? ?? ???? ????

???:?? ?? ?? ???????? ?? ??? ???? ?? Microsoft ???????? ???? ?? ??????? ?? ???????? ?????? ?? ?? ??????? ?? ???? ??????? ?? ???? ???? ???? ?????? ?? initial ??? ?????? ??? ????????????????? ??????? ????????

???????? ???? ??? ????

???????? ???????? ??????? ????? ???? ?? ??? ????? ????? ?? ????? ???? ??:
  1. ?? ?? self-extracting exe ????? ???, ?? ??????? ?? ?????? ??? ??temp???????? ?? ?????? ???
  2. ???????? ???????? ?? ?? ??????? ??? ??? ?? ?????????? ???????????? ????????????? ???? ?? ???? ??? ????? ??? ????? ?? ??????? ???? ?? ?? ??????? ????
  3. ???????? ???????? ??? ?? ?? SQL ????? ??????? ?? ??? ?????????? ?? ??? ????? ??, ?? ?? ?????? ?? ??? ????? ?????????? ?? ???? enumerates. ?????? ???????? ?? ????? ????? ?? ??? SQL ????? ??????? ??? ?????????? ?? ??????? ???? ????? ?? ???????? ?? ?????? ??? ??? Microsoft ???????? ???? ?? ?????? ?? ???? ???? ?? ?????????? ?? ???? ??? ???? ??????? ????? ?????? ?? ???, ??? ???????? Microsoft SQL Server 2000 ?????? ??? 2 ?? ??????? ?? ???????? ??, ?? ?? ??????? ???? ???? SQL Server 2000 ?????? ??? 2 ?? ???????? ?? ???? ???? ?? ????? If the computer does not have any SQL Server installations that qualify for this hotfix installation, you receive a message similar to the following and the installation is aborted:
    You do not have any instance of SQL installed on this computer that qualifies for this HotFix. Please check version and service pack requirements for this Hotfix.
  4. After you select a particular instance of SQL Server for the hotfix upgrade, the hotfix installer resolves and reads to memory the appropriate folder names and locations that correspond to the SQL Server installation that you selected.
  5. The Setup prompts you for information, such as whether you want to use SQL Server Authentication or Windows Authentication. If you select SQL Server Authentication, you must supply the Setup program with the password for theSAlogon. If you select Windows Authentication, you must be running the Setup program while you are logged on to Windows with a Windows logon account. This logon account must be a part of thesysadminfixed server role for the instance of SQL Server you are upgrading. If you want to use SQL Server Authentication, you must make sure that the instance of SQL Server is configured for Mixed Mode security. Otherwise, the authentication step is not successful and you receive the following error message, even if you supply a validSApassword:
    Invalid login information. Please try again.
  6. After you log in SQL Server by using the logon information from step 5, the Setup program stops both the MSSQLSERVER service and the SQL Server Agent services for the instance that is being upgraded.
  7. Now, the hotfix installer performs the core step of replacing the existing files with the new files that were included with the hotfix. To do this, the program searches the destination computer to verify if the files are really present. If the files exist on the destination computer, it qualifies for a replacement. After a file passes this check, the file version is compared against the source file. For files without a version number, the program uses the time and date information. This creates a list of files that are to be installed.
  8. For each file that is selected for replacement, the file is first backed up to a backup folder. This backup folder will exist in the same folder as the file. Under the backup folder there is a sub-folder that has the same name as the hotfix build number.
    ?????? ?? ???, ??? ?? SQL Server 2000 ???????? 701 ??????? ?? ??? ??? ?? Sqlservr.exe ???? ??????? ????? (C:\Program Files\Microsoft SQL Server\MSSQL\Binn\) ?? ???????????? ???? ???? ?????, ?? ???????? ????? ??? ??? ??????? ?????? C:\Program Files\Microsoft SQL Server\MSSQL\Binn\Backup\0701 ?? ????, ?? ??? backs ?????? ????? ????? ?? ?? ????? ?? ???? ?? ???? ??? ?? ?? ??? ???? ?? ???????? ?? ?? ????? ???

    Likewise, ??? ?? C:\Program Files\Microsoft SQL Server\MSSQL\Binn\Resources\1033 ??? ???????? ???? ?? ??? ?? ?? ???? ????? ?? ??? ????, ?? ??? ???? ?? ????? ????? C:\Program Files\Microsoft SQL Server\MSSQL\Binn\resources\1033\Backup\0701 ?? ???? ????????? ???? ??, ?? ?? ???????? ?? ???? ?????? ?? ???? ??? ?? ???

    ???:??? ?? ?? SQL ????? ??????? ?? ???????? ??????? ?? ????? ????, ?? ?? ??? ??? ?????? ??????? ???, SQL Server ??????? ????????? ?? ?????? ???? ?????? ????? ??????? ????? ???? ???? ?? ???????? ??? ?? ?? ?? ???????? ?? ?????? ???? ?? ????? ??????? ????? ?? ???? ????? ??? ?? ?????? ???? ????? ??? ???? ???, ?????? ?? ???? ??? ?? ????? ?? ?? ???????? ?? Microsoft SQL Server 2000 ?? ???????????? ???? ?? ??? ???? ?????? ?????? ???? ?? ??????
  9. ???????? ??? ?????? ?? ??? ???? ??, ?? ??? ??? ????? ????? ???? ???? ?? ???? held ??????? ?? ?? ?????? ????????? ???????? ?? ?????? ?? ???????????? ?? ??? ????? ??? ??? ???? ??, ?? ???????? aborts ??????? ????, ?? ???? ????? ????? ??????? ???? ??:
    Patching ?? ??? ????? ??????? ??? ?? ?? ?? ???? ???? ????????? ?????? ??????? ???? ??? ??? ??? ????? ?? ??????? ?????? ?? ???? ??? ??????? ???

    ????? ??? ????????? ??? ???? ?? ???????? ??????? ?? ???????? ????? ??? ?????? ??? ???? ??, ???? ???? ???????? ???????? ???? ?? ???? ??? ???????? ??????? ?? ???????? ???? ??? ?????
??? ????????? ????? ???????? ???, ?? ???????? ??? ?????? ??????? ???? ?? ?? ????????? ?? ????? ???

??????? ???????

SQL Server 2000 ??????? ???????

To 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 installations

For 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/Active

Follow these steps for an Active/Active installation:
  1. Make sure that the computer node where SQL Server 7.0 was originally installed, controls both the SQL Server resource groups.
  2. On each node of the cluster, run the Failover Setup Wizard utility to remove that Virtual SQL Server.
  3. After unclustering SQL Server, you must run the hotfix executable file on both the nodes, and complete the hotfix installation successfully before you recluster SQL Server.

Active/Passive

Follow these steps for an Active/Passive installation:
  1. Make sure that the computer node, where SQL Server 7.0 was originally installed, controls the SQL Server resources.
  2. On this same computer node, run the Failover Setup Wizard utility to remove that Virtual SQL Server.
  3. After unclustering SQL Server, you must run the hotfix EXE on the primary node only, and complete the hotfix installation successfully before you recluster SQL Server.

Command line parameters

Here is a list of the command line parameters that are available with this hotfix package.
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.
???:?? ????? ?? ???? ???start /waitstandard Windows command line prefix in front of the command to return control to the command prompt after the hotfix installer completes.

Command line examples

  • The command line syntax for an unattended installation of a hotfix on a default instance of SQL Server with the self-extraction progress dialog box disabled is:
    8.00.0701_enu.exe /s /a /q
    Because no authentication information is provided in the command line, a default Windows Authentication logon is used.
  • The command line syntax for an unattended installation of a hotfix on a named instance of SQL Server is:
    8.00.0701_enu.exe /a /q INSTANCENAME=FRIDAY SAPWD=MyPwd
    where FRIDAY is the name of SQL Server 2000 instance. The installation will fail if the INSTANCENAME parameter is supplied as servername\instancename.
  • The command line syntax for an unattended installation of a hotfix by using thestart /waitoption is:
    start /wait 8.00.0701_enu.exe /s /a /q INSTANCENAME=sqlinstance02

How to perform an unattended installation

An 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:
start /wait 8.00.0701_enu.exe /q instancename=inst1

Log file

Every 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:

SQLHotfix?.???

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:
INSTALL SUCCESS
Similarly this message means a failure has occurred during the hotfix installation:
INSTALL FAILURE
This message indicates that the installation was canceled in the middle of the setup process, and the installation was aborted:
User canceled the installation
For failed installations, a corresponding error code is written to the hotfix installer log.

How to remove or rollback the hotfix

If 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:.

??????????The following steps involve rebuilding your??????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:
  1. Detach all user databases. For more information, see the "Attaching and Detaching Databases" topic in SQL Server 7.0 Books Online, or the "How to attach and detach a database (Enterprise Manager)" topic in SQL Server 2000 Books Online.
    ???:If any of the databases are involved in replication, you must first disable publishing and distribution. For more information, see the "Disabling Publishing and Distribution" topic in SQL Server Books Online.
  2. Stop all SQL Server services (that is, MSSQLServer, SQLServerAgent, Microsoft Distributed Transaction Coordinator [MS-DTC], Microsoft Search).
  3. As a safety factor, copy the????:folder to a safe location. If you have data and log files in a separate folder, other than the default????:folder, also copy those files.
  4. Search the computer for the backup folder, and replace the new versions of all files with the old versions.
  5. Rebuild the?????????????:.
  6. ???????????? ??????????,????, ??msdb??????? ?? ?? ??????? ?? ???? ????? ?? ???????? ?? ???? ???? ?? ???? ?? ?? ??? ?? attaches ????: ?? ???? ???? ?? ????? ?? ??????? ??? ?? ???? ?? ?????????? ??????? ??? ????? ??????? ?? ????? ????? ?? ??? ???? ?? ???? ?? ?????????? ??????? ??????? ?????
  7. ??? ?? ?????-??? ?????? ??, ?????-??? ?????? ?? ???????????? ???? ?? ?????-??? ?????? ?? ??? ?? ?????????? ????? ???? ??????? ?? ???, ????? ???? ?? Microsoft ???????? ???? ??? ?????:
    240867?? ???? ?? ????????? ?????, ?? ?????-??? ?????? ????????? ?? ??????? ?? ????? ???? ?? ??? ???? ????
  8. ???? ????????? ?? ????? ???? ??? ?? ?????? ???????? ????????? ???????? ??? ???
  9. ??? ?? SQL ??? ?? ????? ????, ???? ???????? SQL ???? ???? ??????? ?? ???, Microsoft ???????? ??? ?????????? ???? ?????::
    263556SQL ??? ?? ???????? ???? ????

???

???? ID: 330391 - ????? ???????: 04 ?????? 2010 - ??????: 2.0
???? ???? ???? ??:
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 7.0 Standard Edition
??????: 
kbhowto kbinfo kbmt KB330391 KbMthi
???? ?????? ????????
??????????: ?? ???? ?? ???? ??????? ?? ????? ?? Microsoft ????-?????? ?????????? ?????? ?????? ???? ??? ??. Microsoft ???? ??? ????-???????? ?? ????-???????? ????? ?????? ?? ???? ???????? ???? ?? ???? ????? ????? ??? ?? ??? ?????? ?? ???? ???? ???? ??? ????? ??. ???????, ????-???????? ???? ????? ???? ???? ???? ???. ?????, ????????, ?????-???? ?? ??????? ?? ???????? ?? ???? ???, ???? ?? ??? ?????? ???? ???? ??? ????? ??? ?? ???? ??. Microsoft ??????? ??? ???? ?? ?????? ?? ??????????, ????????? ?? ??? ?????? ?? ???? ????? ?? ???? ???????? ?? ??? ???? ????? ?? ??? ????????? ???? ??. Microsoft ????-?????? ?????????? ?? ????? ?????? ?? ?? ??? ??.
?????????? ?? ??????? ????????? ??????? ??:330391

??????????? ???

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com