Читаем SP3readme.htm
Desktop Engine Setup Arguments
Desktop Engine Setup supports the following setup parameters in SP3.

Parameter name Description
ALLOWXDBCHAINING=1 Enables cross-database ownership chaining. For more information, see Section 5.1.11 Cross-Database Ownership Chaining.
BLANKSAPWD=1 Overrides the default behavior of the installer, which is to prohibit installation with a blank sa password. If you set BLANKSAPWD=1, the installer allows installation with a blank sa password.

Warning The use of blank passwords is strongly discouraged.


INSTANCENAME=
instance_name
Specifies the name for the instance. If no instance name is specified, the default instance name MSSQLSERVER is used.
SAPWD=sa_password Specifies the sa password. This option can be used for new installations. Unlike other properties, the SAPWD property is hidden and the value is not written to the log file.
SECURITYMODE=SQL Specifies that the instance use SQL Server Authentication. In Windows NT 4.0, Windows 2000, or Windows XP, if SECURITYMODE=SQL is not specified, Windows Authentication is used and the Windows local administrator's group is added to the SQL Server sysadmin fixed server role.

Important When possible, use Windows Authentication.


UPGRADEUSER=sa Specifies the login to be used when you upgrade Desktop Engine using SQL Server Authentication. The login must be a member of the sysadmin fixed server role.
UPGRADEPWD=
sa_password
Specifies the password for the login that is used when you upgrade Desktop Engine using SQL Server Authentication.
UPGRADE=1 Used when upgrading an instance of Microsoft Desktop Engine version 1.0 to SQL Server 2000 Desktop Engine SP3. The only value supported is 1.


Setup parameters can be specified either in the command line or in an .ini file. For information, see the topic "Customizing Desktop Engine Setup.exe" in SQL Server Books Online.


Note When using the SQL Server 2000 Desktop Engine merge modules as an integrated part of a custom setup, you may not be able to customize the Desktop Engine installation using these command-line parameters. For more information, see Knowledge Base article 810826.



Important Avoid storing credentials in an .ini file.


The following setup switches are used when upgrading, installing, or uninstalling Desktop Engine.

Switch name Description
/upgradesp <setup_path>\SqlRunXX.msi | SQLRUN For SP3 and later, this switch replaces the /p switch that you use when specifying the location of packages. When upgrading to SP3, if you know the number of the original MSI that was used to install Desktop Engine, specify it along with the full path to the location of the SP3 .msi file with the same name. Or, you can specify SQLRUN if you specify your instance name with the INSTANCENAME parameter. For examples of how to use this new switch, see the following section.
/l*v [filename] This standard setup switch is useful when troubleshooting an installation. It specifies that a verbose log be created. If filename is specified, the log is stored in the file specified.
/x package_name This standard setup switch is used when uninstalling Desktop Engine. You must specify the name of the Windows Installer installation package (.msi) file that was used to install the instance of Desktop Engine.


For information about other Setup arguments, see the topic "Customizing Desktop Engine Setup.exe" in SQL Server Books Online.

Upgrading an Existing Instance of Desktop Engine
SP3 introduces a new switch for upgrading Desktop Engine. The /upgradesp switch replaces the /p switch. When using this new switch, you have two options, depending on the information that you have about the instance of Desktop Engine that you are upgrading. You must either know the instance name (the default is MSSQLSERVER) or you must know which .msi file was originally used to install Desktop Engine.

If you know the instance name, use the /upgradesp switch as shown in the following example:

Setup.exe /upgradesp SQLRUN INSTANCENAME=instance_name SECURITYMODE=SQL
UPGRADEUSER=<username> UPGRADEPWD=<password>

Important If you use an .ini file during setup, avoid storing credentials in the .ini file.


In this case, the installer uses the instance name to determine which .msi file was originally used to install Desktop Engine.


Note When upgrading the default instance, you do not have to specify INSTANCENAME.


Desktop Engine can be installed with one of 16 .msi files (SqlRun01.msi through SqlRun16.msi). If you know the name of the original .msi file that was used to install Desktop Engine, you can specify it along with the complete path to the SP3 .msi file of the same name, as shown in the following example:

Setup.exe /upgradesp c:\SQL2KSP3\MSDE\Setup\SqlRun03.msi SECURITYMODE=SQL
UPGRADEUSER=<username> UPGRADEPWD=<password>

Important If you use an .ini file during setup, avoid storing credentials in the .ini file.


In this example, C:\SQL2KSP3\MSDE\Setup represents the location of the SP3 .msi files and SqlRun03.msi is the name of the .msi file used in the original installation.

If you do not know either the instance name or the name of the original .msi file, see Microsoft Knowledge Base article 311762. This article describes how to determine the name of the original .msi file. You can access the article from the Microsoft Product Support Services Knowledge Base.

Upgrading SQL Server 2000 Desktop Engine
To upgrade SQL Server 2000 Desktop Engine

Run Setup.exe to initiate setup. (Do not run Setup directly from the .msi file.)


If the instance name is known, use /upgradesp SQLRUN INSTANCENAME=instance_name
-or-

If the name of the original .msi file is known, use /upgradesp and specify the name of the .msi file along with the complete path to the SP3 .msi file of the same name.

Specify SECURITYMODE=SQL.


Use the UPGRADEUSER parameter to specify a login account for Setup to use that is a member of the sysadmin fixed server role.


Use the UPGRADEPWD setup parameter to specify the password for the chosen login account.

Important If you use an .ini file during setup, avoid storing credentials in the .ini file.



Note If you use BLANKSAPWD=1, you are not required to specify SECURITYMODE=SQL or UPGRADEUSER and UPGRADEPWD.



Warning The use of blank passwords is strongly discouraged.



Note When upgrading Desktop Engine on a computer running Windows 98 or Windows Millennium Edition, the instance of Desktop Engine that you are upgrading must be stopped before starting Setup.


Upgrading from Desktop Engine version 1.0
To upgrade from Desktop Engine version 1.0

This service pack supports the capability to upgrade an instance of Desktop Engine version 1.0 directly to SQL Server 2000 Desktop Engine SP3. To upgrade Desktop Engine:

Stop the instance of Desktop Engine 1.0 that you are upgrading.


Run Setup.exe to initiate setup. (Do not run Setup directly from the .msi file.)


Specify UPGRADE=1
If you are using SQL Server Authentication, you also need to do the following:

Specify SECURITYMODE=SQL.


Use the UPGRADEUSER parameter to specify a login account for Setup to use that is a member of the sysadmin fixed server role.


Use the UPGRADEPWD setup parameter to specify the password for the chosen login account.

Note If you use BLANKSAPWD=1, you are not required to specify SECURITYMODE=SQL or UPGRADEUSER and UPGRADEPWD.



Warning The use of blank passwords is strongly discouraged.



Important If you use an .ini file during setup, avoid storing credentials in the .ini file.


Installing a New Instance of Desktop Engine
SP3 allows you to install a new instance of Desktop Engine.

To install a new instance of Desktop Engine

Run Setup.exe to initiate Setup. (Do not run Setup directly from the .msi file.)


If you are using SQL Server Authentication, specify SECURITYMODE=SQL.


Regardless of the authentication mode, you must do one of the following:
Specify a password for the sa login using the SAPWD setup parameter.


Specify the BLANKSAPWD=1 parameter.

Note If both SAPWD and BLANKSAPWD are specified, SAPWD takes precedence and BLANKSAPWD is ignored.



Important If you are using an .ini file during setup, avoid storing credentials in the .ini file.



Warning The use of blank passwords is strongly discouraged.


For additional information, see the topic "Installing Desktop Engine" in SQL Server Books Online. For information about the appropriate uses of Desktop Engine, see the Microsoft SQL Server Web site for Desktop Engine.

Это для того чтобы не засорять EM лишними серверами. Кроме того не все видны broadcast...