How to: Install SQL Server 2008 from the Command Prompt

SQL Server Setup

previous page next page

Before you run SQL Server Setup, review Planning a SQL Server Installation.

Installing a new instance of SQL Server from the command prompt enables you to specify the features to install and how they should be configured. You can also specify silent, basic, or full interaction with the Setup user interface.

Command prompt installation is supported in the following scenarios:

  • Installing, upgrading, or removing an instance and shared components of SQL Server 2008 on a local computer with syntax and parameters specified at the command prompt.
  • Installing, upgrading, or removing a failover cluster instance.
  • Upgrading from one SQL Server 2008 edition to another edition of SQL Server 2008.
  • Installing an instance of SQL Server 2008 on a local computer with syntax and parameters specified in a configuration file. You can use this method to copy an installation configuration to multiple computers, or to install multiple nodes of a failover cluster installation.

When you install SQL Server from the command prompt, specify Setup parameters for your installation at the command prompt as part of your installation syntax.

Note:
For local installations, you must run Setup as an administrator. If you install SQL Server from a remote share, you must use a domain account that has read and execute permissions on the remote share. For failover cluster installations, you must be a local administrator with permissions to login as a service, and to act as part of the operating system on all failover cluster nodes.

Proper Use of Setup Parameters

Use the following guidelines to develop installation commands with correct syntax:

Copy Code
/PARAMETER
/PARAMETER=true/false

One exception is /FEATURES, which is a multi-value parameter, but its format is

  • /FEATURES=AS,RS,IS with no space, comma-delimited

Note the use of escaping characters:

  • /INSTANCEDIR=c:\PathName is supported.
  • /INSTANCEDIR=c:\PathName\ is supported
  • /INSTANCEDIR="c:\PathName\\" is supported.
  • /INSTANCEDIR="c:\PathName\" is not supported.

Sample Syntax

Use the following sample scripts to install SQL Server components at the command prompt. The scripts provide command prompt syntax to install SQL Server in typical user scenarios. Test and modify samples to meet the needs of your organization.

Supported use of Setup parameters

Parameter Use

Basic installation scenarios, including Database Engine Services and Management Tools

Installation Scripts for Basic Installation Scenarios

Failover cluster installation scenarios

Installation Scripts for Failover Cluster Scenarios

Analysis Services installation scenarios

Installation Scripts for Analysis Services Installation Scenarios

Reporting Services installation scenarios

Installation Options and Scripts for Reporting Services

Integration Services installation scenarios

Installation Scripts for Analysis Services Installation Scenarios

Reference documentation for installation parameters

Installation parameters

Compare Setup Parameters between SQL Server Versions

Parameters from previous SQL Server versions

Installation Scripts for Basic Installation Scenarios

Test and modify the following installation scripts to meet the needs of your organization.

To install a new, stand-alone instance with all SQL Server components.

  1. Insert the SQL Server 2008 installation media into the disk drive and open the root folder.

  2. Run the following command at the command prompt:

    Copy Code
    Setup.exe /q /ACTION=Install /FEATURES=SQL,AS,RS,IS,Tools,BIDS,BOL /INSTANCENAME=MSSQLSERVER /SECURITYMODE=SQL /SQLSYSADMINACCOUNTS="Builtin\Administrators" /SAPWD="StrongPassword" /SQLSVCACCOUNT="DomainName\UserName" /SQLSVCPASSWORD="StrongPassword" /AGTSVCACCOUNT="DomainName\UserName" /AGTSVCPASSWORD="StrongPassword" /ASSYSADMINACCOUNTS="Builtin\Administrators" /ASSVCACCOUNT="DomainName\UserName" /ASSVCPASSWORD="StrongPassword" /RSSVCACCOUNT="DomainName\UserName" /RSSVCPASSWORD="StrongPassword" /SQLBROWSERACCOUNT="DomainName\UserName" /SQLBROWSERPASSWORD="StrongPassword" /ISSVCACCOUNT="NT Authority\Network Service"
    Important:
    Do not use a blank password. Use a strong password.

    Note:
    For a default instance, specify "MSSQLSERVER" for the /INSTANCENAME parameter. For a named instance, specify the instance name.

    For more information about service account configuration, see Setting Up Windows Service Accounts. For more information about log files, see How to: View SQL Server 2008 Setup Log Files.

 To install a new, stand-alone instance with the SQL Server Database Engine, Replication, and Full-Text Search components.

  1. Insert the SQL Server 2008 installation media into the disk drive and open the root folder.

  2. Run the following command at the command prompt:

    Copy Code
    Setup.exe /q /ACTION=Install /FEATURES=SQL /INSTANCENAME=MSSQLSERVER /SQLSVCACCOUNT="DomainName\UserName" /SQLSVCPASSWORD="StrongPassword" /SQLSYSADMINACCOUNTS="DomainName\UserName" /AGTSVCACCOUNT="NT AUTHORITY\Network Service"

Important   Do not use a blank password. Use a strong password.

Note:
For a default instance, specify "MSSQLSERVER" for the /INSTANCENAME parameter. For a named instance, specify the instance name.

To install SQL Server Management Tools only.

  1. Insert the SQL Server 2008 installation media into the disk drive and open the root folder.

  2. Run the following command at the command prompt:

    Copy Code
    Setup.exe /Action=Install /FEATURES=Tools

 To install SQL Server Express.

  1. Insert the SQL Server 2008 installation media into the disk drive and open the root folder.

  2. Run the following command at the command prompt:

    Copy Code
    Setup.exe /q /FEATURES=SQL_Tools /INSTANCE=Express /SQLSVCACCOUNT="DomainName\UserName" /SQLSVCPASSWORD="StrongPassword" /SQLSYSADMINACCOUNTS="BUILTIN\Administrators"
Use the /ENABLERANU parameter to enable RANU
Use the /ADDCURRENTUSERASSQLADMIN parameter to provision the user in the sysadmin role.

 To upgrade an existing instance or failover cluster node from SQL Server 2000 or SQL Server 2005.

  1. Before you begin, review the upgrade documentation in Using Upgrade Advisor to Prepare for Upgrades and Backward Compatibility. It is not necessary to specify the features to upgrade.

  2. Insert the SQL Server 2008 installation media into the disk drive and open the root folder.

  3. Run the following command at the command prompt:

    Copy Code
    Setup.exe /q /ACTION=upgrade /INSTANCENAME=MSSQLSERVER /SQLSYSADMINACCOUNTS="BUILTIN\ADMINISTRATORS" /RSUPGRADEDATABASEACCOUNT="<Provide a SQL Server logon account that can connect to the report server during upgrade>" /RSUPGRADEPASSWORD="<Provide a password for the report server upgrade account>"/ISSVCAccount="NT Authority\Network Service"

    If upgrading a node of a failover cluster instance, use the /FAILOVERCLUSTERROLLOWNERSHIP parameter to control the failover behavior before the upgrade operation takes to node offline. Use of this parameter is as follows:

    • /FAILOVERCLUSTERROLLOWNERSHIP=0 will not roll cluster ownership to upgraded nodes, and do not add this node to the list of possible owners of the SQL Server cluster at the end of upgrade.
    • /FAILOVERCLUSTERROLLOWNERSHIP=1 will roll cluster ownership to upgraded nodes, and will add this node to the list of possible owners of the SQL Server cluster at the end of upgrade.
    • /FAILOVERCLUSTERROLLOWNERSHIP=2 is the default setting. It will be used if this parameter is not specified. This setting indicates that SQL Server Setup will manage cluster ownership as needed.

  4. To upgrade shared components only, run the following command at a command prompt:

    Copy Code
    Setup.exe /q /ACTION=upgrade

Important   Do not use a blank password. Use a strong password.

Note:
For a default instance, specify "MSSQLSERVER" for the /INSTANCENAME parameter. For a named instance, specify the instance name.

To upgrade an existing instance of SQL Server 2008 to a different edition of SQL Server 2008.

  1. Insert the SQL Server 2008 installation media into the disk drive and open the root folder.

  2. Run the following command at the command prompt:

    Copy Code
    Setup.exe /q /ACTION=editionupgrade /INSTANCENAME=MSSQLSERVER /PID=<PID key for new edition>"

Important   Do not use a blank password. Use a strong password.

Note:
For a default instance, specify "MSSQLSERVER" for the /INSTANCENAME parameter. For a named instance, specify the instance name. If the instance name is not specified, only the shared components will be upgraded.

To install SQL Server 2008 by using a configuration file.

  1. Insert the SQL Server 2008 installation media into the disk drive and open the root folder.

  2. Run the following command at the command prompt:

    Copy Code
    Setup.exe /q /ACTION=Install /Configurationfile=<path to ConfigurationFile.ini file>

    After running SQL Server 2008 Setup, a configuration file is generated and saved by default to <drive>:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\<YYYYMMDD_HHMMSS\ConfigurationFile.ini. Open the file to see descriptions of Setup parameters and settings for the installation that was completed. You can use the configuration file to reproduce additional instances or to install additional nodes of a failover cluster installation.

    For more information about log files, see How to: View SQL Server 2008 Setup Log Files.

To add components to an existing SQL Server instance.

  1. Insert the SQL Server 2008 installation media into the disk drive and open the root folder.

  2. Run the following command at the command prompt:

    Copy Code
    Setup.exe /q /ACTION=Install /INSTANCENAME=MSSQLSERVER /FEATURES=<Feature list>

    Note   To add features to a named instance, use the instance name instead of "MSSQLSERVER" in the example above.

 To uninstall an existing SQL Server instance.

  1. Insert the SQL Server installation media into the disk drive.

  2. At a command prompt, navigate to the following directory: %Program Files%\Microsoft SQL Server\100\Setup Bootstrap and type the following command at the command prompt:

    Copy Code
    Setup100.exe /Action=Uninstall /FEATURES=SQL,AS,RS,IS,Tools /INSTANCENAME=MSSQLSERVER

    Note   To remove a named instance, use the instance name instead of "MSSQLSERVER" in the example above.

Installation Scripts for Failover Cluster Installation Scenarios

There are two options for SQL Server Failover Cluster installation:

  • Integrated installation installs and configures a single-node failover cluster instance in a single step.
  • Advanced installation, also known as Enterprise installation, consists of 2 steps: preparing a failover cluster instance, and then completing the installation to create a single-node failover cluster instance.

Before you install a SQL Server failover cluster instance, review the following topics:

Test and modify the following failover cluster installation scripts to meet the needs of your organization.

To install an integrated, single-node SQL Server failover cluster with the Database Engine.

  1. Insert the SQL Server 2008 installation media into the disk drive and open the root folder.

  2. Run the following command at a command prompt:

    Copy Code
    setup.exe /q /ACTION=InstallFailoverCluster /FEATURES=SQL /INSTANCENAME="<Insert Instance Name>" [/INSTANCEIDSUFFIX="<Insert InstanceID Suffix>"] /INSTANCEDIR="C:\Program Files\Microsoft SQL Server" /INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server" /SQLSVCACCOUNT="DomainName\UserName" /SQLSVCPASSWORD="XXXXXX" /AGTSVCACCOUNT="DomainName\UserName" /AGTSVCPASSWORD="XXXXXX" /SQLDOMAINGROUP="DomainName\DomainGroup" /INSTALLSQLDATADIR="<Drive>:\<Path>\MSSQLSERVER" /SQLCOLLATION="CollationName"; default is SQL_Latin1_General_CP1_CS_AS" /FAILOVERCLUSTERGROUP="<Insert new Cluster Group name>" /FAILOVERCLUSTERDISKS="<Cluster Disk Resource Name - for example, 'Disk S:'" /FAILOVERCLUSTERIPADDRESSES="IPv4;XXX.XXX.XXX.XXX;Local Area Connection;xxx.xxx.xxx.x" /FAILOVERCLUSTERNETWORKNAME="<Insert Failover Cluster Instance Name>" /SQLSYSADMINACCOUNTS=" DomainName\UserName " [/SECURITYMODE=SQL /SAPWD="StrongPassword"]

 To install a single-node SQL Server failover cluster with Analysis Services.

  1. Insert the SQL Server 2008 installation media into the disk drive and open the root folder.

  2. Run the following command at the command prompt:

    Copy Code
    setup.exe /q /ACTION=InstallFailoverCluster /FEATURES=AS /INSTANCENAME="<Insert Instance Name>" [/INSTANCEIDSUFFIX="<Insert InstanceID Suffix>"] /ASSYSADMINACCOUNTS="DomainName\UserName" /ASSVCACCOUNT="DomainName\UserName" /ASSVCPASSWORD="xxxxx" /ASDOMAINGROUP="DomainName\DomainGroup" /ASDATADIR="<Drive>:\Data" /ASLOGDIR="<Drive>:\Log" /ASBACKUPDIR="<Drive>:\Backup" /ASCONFIGDIR="<Drive>:\Config" /ASTEMPDIR="<Drive>:\Temp" /FAILOVERCLUSTERGROUP="<Insert new Cluster Group name>" /FAILOVERCLUSTERDISKS="<Drive>:" /FAILOVERCLUSTERIPADDRESSES="IPv4; xxx.xxx.xxx.xxx;Local Area Connection;xxx.xxx.xxx.x" /FAILOVERCLUSTERNETWORKNAME="<Insert Failover Cluster Instance Name>" /INDICATEPROGRESS

 To install a single-node SQL Server failover cluster instance with the Database Engine and Analysis Services, default instance.

  1. Insert the SQL Server 2008 installation media into the disk drive and open the root folder.

  2. Run the following command at the command prompt:

    Copy Code
    setup.exe /q /ACTION=InstallFailoverCluster /InstanceName=MSSQLSERVER /INDICATEPROGRESS /ASSYSADMINACCOUNTS="DomainName\UserName" /ASDATADIR=<Drive>:\OLAP\Data /ASLOGDIR=<Drive>:\OLAP\Log /ASBACKUPDIR=<Drive>:\OLAP\Backup /ASCONFIGDIR=<Drive>:\OLAP\Config /ASTEMPDIR=<Drive>:\OLAP\Temp /FAILOVERCLUSTERDISKS="<Cluster Disk Resource Name - e.g., 'Disk S:'" /FAILOVERCLUSTERNETWORKNAME="<Insert Network Name>" /FAILOVERCLUSTERIPADDRESSES="IPv4;xx.xxx.xx.xx;Local Area Connection;xxx.xxx.xxx.x" /FAILOVERCLUSTERGROUP="MSSQLSERVER" /Features=AS,SQL /ASSVCACCOUNT="DomainName\UserName" /ASSVCPASSWORD="xxxxxxxxxxx" /ASDOMAINGROUP="DomainName\DomainGroup" /AGTSVCACCOUNT="DomainName\UserName" /AGTSVCPASSWORD="xxxxxxxxxxx" /SQLDOMAINGROUP="DomainName\DomainGroup" /INSTALLSQLDATADIR="<Drive>:\<Path>\MSSQLSERVER" /SQLCOLLATION="SQL_Latin1_General_CP1_CS_AS" /SQLSVCACCOUNT="DomainName\UserName" /SQLSVCPASSWORD="xxxxxxxxxxx" /SQLSYSADMINACCOUNTS="DomainName\UserName
 To install a single-node SQL Server failover cluster instance with the Database Engine and Analysis Services, named instance.

  1. Insert the SQL Server 2008 installation media into the disk drive and open the root folder.

  2. Run the following command at the command prompt:

    Copy Code
    setup.exe /q /ACTION=InstallFailoverCluster /InstanceName=INSTANCE NAME /INDICATEPROGRESS /ASSYSADMINACCOUNTS="DomainName\UserName" /ASDATADIR=<Drive>:\OLAP\Data /ASLOGDIR=<Drive>:\OLAP\Log /ASBACKUPDIR=<Drive>:\OLAP\Backup /ASCONFIGDIR=<Drive>:\OLAP\Config /ASTEMPDIR=<Drive>:\OLAP\Temp /FAILOVERCLUSTERDISKS="<Clister Disk Resource Name - e.g., 'Disk S:'" /FAILOVERCLUSTERNETWORKNAME="<Insert Network Name>" /FAILOVERCLUSTERIPADDRESSES="IPv4;xx.xxx.xx.xx;Local Area Connection;xxx.xxx.xxx.x" /FAILOVERCLUSTERGROUP="NAMED_INSTANCE" /Features=AS,SQL /ASSVCACCOUNT="DomainName\UserName" /ASSVCPASSWORD="xxxxxxxxxxx" /ASDOMAINGROUP="DomainName\DomainGroup" /AGTSVCACCOUNT="DomainName\UserName" /AGTSVCPASSWORD="xxxxxxxxxxx" /SQLDOMAINGROUP="DomainName\DomainGroup" /INSTALLSQLDATADIR="<Drive>:\<Path>\<INSTANCE NAME>\" /SQLCOLLATION="SQL_Latin1_General_CP1_CS_AS" /SQLSVCACCOUNT="DomainName\UserName" /SQLSVCPASSWORD="xxxxxxxxxxx" /SQLSYSADMINACCOUNTS="DomainName\UserName"

Advanced Scenarios for Failover Cluster Installation:

The following two examples use two steps to create a Database Engine failover cluster instance: one step to prepare the failover cluster instance, and another step to complete the process.

Test and modify the installation scripts to meet the needs of your organization.

To perform the "Preparation" step of a failover cluster advanced installation scenario for the Database Engine. This is step 1 of 2.

  1. Insert the SQL Server 2008 installation media into the disk drive and open the root folder.

  2. Run the following command at the command prompt:

    Copy Code
    Setup.exe /q /ACTION=PrepareFailoverCluster /FEATURES=SQL /INSTANCENAME="<Insert Instance Name>" [/INSTANCEIDSUFFIX="<Insert InstanceID Suffix>"] /INSTANCEDIR="<Drive>:\Program Files\Microsoft SQL Server" /INSTALLSHAREDDIR="<Drive>:\Program Files\Microsoft SQL Server" /SQLSVCACCOUNT="DomainName\UserName" /SQLSVCPASSWORD="XXXXXX" /AGTSVCACCOUNT="DomainName\UserName" /AGTSVCPASSWORD="XXXXXX" /SQLDOMAINGROUP="DomainName\DomainGroup"

 To perform the "Completion" step of a failover cluster advanced installation scenario for the Database Engine. This is step 2 of 2. Run the following command on the computer that will be the active node in the failover cluster to make it useable. You must run the "CompleteFailoverCluster" action on the node that owns the shared disk in the SQL Server failover cluster.

  1. Insert the SQL Server 2008 installation media into the disk drive and open the root folder.

  2. Run the following command at the command prompt:

    Copy Code
    setup.exe /q /ACTION=CompleteFailoverCluster /INSTANCENAME="<Insert Instance Name>" /FAILOVERCLUSTERNETWORKNAME="<Insert FOI Name>" /FAILOVERCLUSTERGROUP="Insert New Cluster Group>" /FAILOVERCLUSTERDISKS="<Cluster Disk Resource Name - e.g., 'Disk S:'>" /FAILOVERCLUSTERIPADDRESSES="IPv4;XXX.XXX.XXX.XXX;Local Area Connection;xxx.xxx.xxx.x" /INSTALLSQLDATADIR="<Drive>:\<Path>\MSSQLSERVER" /SQLCOLLATION="SQL_Latin1_General_CP1_CS_AS" /SQLSYSADMINACCOUNTS="DomainName\UserName" [/SECURITYMODE=SQL /SAPWD="StrongPassword"]

The following two examples use two steps to create an Analysis Services failover cluster instance. Test and modify the installation scripts to meet the needs of your organization.

To perform the "Preparation" step of a failover cluster advanced installation scenario for Analysis Services. This is step 1 of 2.

  1. Insert the SQL Server 2008 installation media into the disk drive and open the root folder.

  2. Run the following command at the command prompt:

    Copy Code
    setup.exe /q /ACTION=PrepareFailoverCluster /FEATURES=AS /InstanceName="<Insert Instance Name>" /ASSVCACCOUNT="DomainName\UserName" /ASSVCPASSWORD="xxxxx" /ASDOMAINGROUP="DomainName\DomainGroup" /INDICATEPROGRESS

 To perform the "Completion" step of a failover cluster advanced installation scenario for Analysis Services. This is step 2 of 2. Run the following command on the computer that will be the active node in the failover cluster to make it useable. You must run the "CompleteFailoverCluster" action on the node that owns the shared disk in the Analysis Services failover cluster.

  1. Insert the SQL Server 2008 installation media into the disk drive and open the root folder.

  2. Run the following command at the command prompt:

    Copy Code
    setup.exe /q /ACTION=CompleteFailoverCluster /INSTANCENAME="<Insert Instance Name>" /FAILOVERCLUSTERNETWORKNAME="<Insert FOI Name>" /FAILOVERCLUSTERGROUP="<Insert New Cluster Group>" /FAILOVERCLUSTERDISKS="<Cluster Disk Resource Name - for example, 'Disk S:'>" /FAILOVERCLUSTERIPADDRESSES="IPv4;xxx.xxx.xxx.xxx;Local Area Connection;xxx.xxx.xxx.x" /ASSYSADMINACCOUNTS="DomainName\UserName" /ASDATADIR="<Drive>:\NEW_KATMAI\Data" /ASLOGDIR="<Drive>:\NEW_KATMAI\Log" /ASBACKUPDIR="Drive:\NEW_KATMAI\Backup" /ASCONFIGDIR="<Drive>:\NEW_KATMAI\Config" /ASTEMPDIR="<Drive>:\NEW_KATMAI\Temp" /INDICATEPROGRESS

The following two examples use two steps to create a SQL Server failover cluster instance with the Database Engine and Analysis Services. Test and modify the installation scripts to meet the needs of your organization.

To perform the "Preparation" step of a failover cluster advanced installation scenario for the Database Engine and Analysis Services. This is step 1 of 2.

  1. Insert the SQL Server 2008 installation media into the disk drive and open the root folder.

  2. Run the following command at the command prompt to prepare a default instance:

    Copy Code
    setup.exe /q /ACTION=PrepareFailoverCluster /InstanceName=MSSQLSERVER /Features=AS,SQL /INDICATEPROGRESS /ASSVCACCOUNT="DomainName\UserName" /ASSVCPASSWORD="xxxxxxxxxxx" /ASDOMAINGROUP="DomainName\DomainGroup" /SQLSVCACCOUNT="DomainName\UserName" /SQLSVCPASSWORD="xxxxxxxxxxx" /SQLDOMAINGROUP="DomainName\DomainGroup" /AGTSVCACCOUNT="DomainName\UserName" /AGTSVCPASSWORD="xxxxxxxxxxx"

Run the following command at the command prompt to prepare a named instance:

To perform the "Completion" step of a failover cluster advanced installation scenario for the Database Engine and Analysis Services. This is step 2 of 2. Run the following command on the computer that will be the active node in the failover cluster to make it useable. You must run the "CompleteFailoverCluster" action on the node that owns the shared disk in the Analysis Services failover cluster.

  1. Insert the SQL Server 2008 installation media into the disk drive and open the root folder.

  2. Run the following command at the command prompt to complete failover cluster installation for a default instance:

    Copy Code
    setup.exe /q /ACTION=CompleteFailoverCluster /InstanceName=MSSQLSERVER /INDICATEPROGRESS /ASSYSADMINACCOUNTS="DomainName\Username" /ASDATADIR=<Drive>:\OLAP\Data /ASLOGDIR=<Drive>:\OLAP\Log /ASBACKUPDIR=<Drive>:\OLAP\Backup /ASCONFIGDIR=<Drive>:\OLAP\Config /ASTEMPDIR=<Drive>:\OLAP\Temp /FAILOVERCLUSTERDISKS="<Cluster Disk Resource Name - for example, 'Disk S:'>:" /FAILOVERCLUSTERNETWORKNAME="<Insert FOI Network Name>" /FAILOVERCLUSTERIPADDRESSES="IPv4;xx.xxx.xx.xx;Local Area Connection;xxx.xxx.xxx.x" /FAILOVERCLUSTERGROUP="MSSQLSERVER" /INSTALLSQLDATADIR="<Drive>:\<Path>\MSSQLSERVER" /SQLCOLLATION="SQL_Latin1_General_CP1_CS_AS" /SQLSYSADMINACCOUNTS="DomainName\UserName"

Run the following command at the command prompt to complete failover cluster installation for a named instance:

Add Node and Remove Node Scenarios:

Use the following syntax to add or remove nodes from an existing SQL Server failover cluster instance. The AddNode action gathers feature and setting information from the active node, installs the necessary components, and joins the new node to the existing SQL Server failover cluster. AddNode can be used for both integrated and advanced scenarios.

Test and modify the installation scripts to meet the needs of your organization.

To add a node to an existing failover cluster instance with the Database Engine.

  1. Insert the SQL Server 2008 installation media into the disk drive and open the root folder.

  2. Run the following command at the command prompt:

    Copy Code
    setup.exe /q /ACTION=AddNode /INSTANCENAME="<Insert Instance Name>" /SQLSVCACCOUNT="<SQL account used on other nodes>" /SQLSVCPASSWORD="<password for SQL account>" /AGTSVCACCOUNT="<SQL Server Agent account used on other nodes>", /AGTSVCPASSWORD="<SQL Server Agent account password>"

 To add a node to an existing failover cluster instance with Analysis Services.

  1. Insert the SQL Server 2008 installation media into the disk drive and open the root folder.

  2. Run the following command at the command prompt:

    Copy Code
    setup.exe /q /ACTION=AddNode /INSTANCENAME="<Insert Instance Name>" /ASSVCACCOUNT="<AS account used on other nodes>" /ASSVCPASSWORD=”<password for AS account>” /INDICATEPROGRESS
 To add a node to an existing failover cluster instance with the Database Engine and Analysis Services.

  1. Insert the SQL Server 2008 installation media into the disk drive and open the root folder.

  2. Run the following command at the command prompt:

    Copy Code
    setup.exe /q /ACTION=AddNode /INSTANCENAME="<Insert Instance Name>" /SQLSVCACCOUNT="<SQL account used on other nodes>" /SQLSVCPASSWORD="<password for SQL account>" /AGTSVCACCOUNT="<SQL Server Agent account used on other nodes>", /AGTSVCPASSWORD="<SQL Server Agent account password>" /ASSVCACCOUNT="<AS account used on other nodes>" /ASSVCPASSWORD=”<password for AS account>” /INDICATEPROGRESS

To completely remove a SQL Server failover cluster instance, use the REMOVENODE action on each failover cluster node. Test and modify the scripts to meet the needs of your organization.

To remove a node from an existing failover cluster instance with the Database Engine.

  1. Insert the SQL Server 2008 installation media into the disk drive and open the root folder.

  2. Run the following command at the command prompt:

    Copy Code
    setup.exe /q /ACTION=RemoveNode /INSTANCENAME="<Insert Instance Name>" [/INDICATEPROGRESS]

 To remove a node from an existing failover cluster instance with Analysis Services.

  1. Insert the SQL Server 2008 installation media into the disk drive and open the root folder.

  2. Run the following command at the command prompt:

    Copy Code
    setup.exe /q /ACTION=RemoveNode /INSTANCENAME="<Insert Instance Name>" [/INDICATEPROGRESS]

 To remove a node from an existing failover cluster instance with the Database Engine and Analysis Services.

  1. Insert the SQL Server 2008 installation media into the disk drive and open the root folder.

  2. Run the following command at the command prompt:

    Copy Code
    setup.exe /q /ACTION=RemoveNode /INSTANCENAME="<Insert Instance Name>" [/INDICATEPROGRESS]

Installation Scripts for Analysis Services

To install or upgrade Analysis Services at a command prompt, specify "AS" as one of the values for the FEATURES command-line option. For example, to install Analysis Services, you would specify /FEATURES=AS on the command line.

The following table shows the parameters available for installing an instance of Analysis Services.

Parameter Default Value Description

ASBACKUPDIR

C:\Program Files\Microsoft SQL Server\<Instance ID>\OLAP\Backup

For example, the Instance ID might look something like this: MSAS10.MSSQLSERVER.

Specifies the folder in which the Analysis Services backup files are stored.

ASCOLLATION

Latin1_General_CI_AS

Specifies the collation setting for Analysis Services.

ASCONFIGDIR

C:\Program Files\Microsoft SQL Server\<Instance ID>\OLAP\Config

Specifies the folder in which the Analysis Services configuration files are installed.

ASDATADIR

C:\Program Files\Microsoft SQL Server\<Instance ID>\OLAP\Data

Specifies the folder in which the Analysis Services cubes are built.

ASLANGUAGE

1033

Specifies the locale identifier (LCID). The value 1033 represents US-English.

ASLOGDIR

C:\Program Files\Microsoft SQL Server\<Instance ID>\OLAP\Log

Specifies the folder in which the Analysis Services log files are stored.

ASPROVIDERMSOLAP

1

Specifies whether the MSOLAP provider can run in process.

ASSVCACCOUNT

local system account

Specifies the MSSQLServerOLAPService service account domain and logon name. Use the argument ASSVCPASSWORD to specify the password that corresponds to the logon name. If you do not specify this argument, the default will be used.

ASSVCPASSWORD

blank

Specifies the MSSQLServerOLAPService service account password that corresponds to the logon name that is specified by the argument ASSVCACCOUNT. Specifying a blank password will cause an error. To use a blank password do not specify this parameter.

ASSVCSTARTUPTYPE

Automatic

Specifies whether the MSSQLServerOLAPService service is started automatically when the Windows operating system is restarted. The options are Automatic, Disabled, or Manual.

ASSYSADMINACCOUNTS

blank

Specifies the MSSQLServerOLAPService administrator account password.

ASTEMPDIR

C:\Program Files\Microsoft SQL Server\<Instance ID>\OLAP\Temp

Specifies the folder in which the Analysis Services temporary files are stored.

ERRORREPORTING

0

Specifies whether error reporting is enabled or disabled. To enable error reporting, specify 1. Otherwise, specify 0.

SQMREPORTING

0

Specifies whether Software Quality Monitoring (SQM) is enabled. To enable SQM reporting, specify 1. Otherwise, specify 0.

Test and modify the following Analysis Services installation scripts to meet the needs of your organization.

To install a new default instance of Analysis Services and Management Tools.

  1. Insert the installation media into the disk drive and open the folder at <CD or DVD drive>:\SQLDev\Servers\, or navigate to the network build folder \\..\SQLDev\Servers\.

  2. Run the following command at a command prompt:

    Copy Code
                    setup.exe /ACTION=install /FEATURES=AS,Tools /INSTANCENAME=MSSQLSERVER /ASSVCACCOUNT =<DomainName\UserName> /ASSVCPASSWORD =<StrongPassword>

    Important   Do not use a blank password. Use a strong password.

 To upgrade an existing instance of SQL Server 2000 Analysis Services or SQL Server 2005 Analysis Services

  1. Insert the installation media into the disk drive and open the folder at <CD or DVD drive>:\SQLDev\Servers\, or navigate to the network build folder \\..\SQLDev\Servers\..

  2. Run the following command at a command prompt:

    Copy Code
                    setup.exe /ACTION=upgrade /FEATURES=AS /INSTANCENAME=<InstanceName>
To repair a broken SQL Server 2008 Analysis Services installation

  1. Insert the installation media into the disk drive and open the folder at <CD or DVD drive>:\SQLDev\Servers\, or navigate to the network build folder \\..\SQLDev\Servers\..

  2. Run the following command at a command prompt:

    Copy Code
                    setup.exe /ACTION=repair /FEATURES=AS /INSTANCENAME=<InstanceName> /ASSVCACCOUNT =<DomainName\UserName> /ASSVCPASSWORD=<StrongPassword>
 To uninstall an instance of Analysis Services

  1. Insert the installation media into the disk drive and open the folder at <CD or DVD drive>:\SQLDev\Servers\, or navigate to the network build folder \\..\SQLDev\Servers\..

  2. Run the following command at a command prompt:

    Copy Code
                    setup.exe /ACTION=uninstall /FEATURES=AS /INSTANCENAME=<InstanceName>

Installation Options and Scripts for Reporting Services

To install or upgrade Reporting Services from the command prompt, specify "RS" as one of the values for the /FEATURES command line option. Reporting Services is instance-aware so you must specify the /INSTANCENAME parameter. Use the following options to configure a Reporting Services installation:

Option Valid Values Required Description

RSInstallMode

FilesOnlyMode

DefaultNativeMode

DefaultSharePointMode

Optional

FilesOnlyMode installs the Reporting Services program files. FilesOnlyMode is the default. If you specify this mode, you must perform all configuration steps by using the Reporting Services Configuration tool after setup is complete. This mode is required if you want to install Reporting Services as a named instance or if you want to use a remote Database Engine instance to host the report server database.

DefaultNativeMode installs and configures the report server using default values for the service account, report server database, and URLs.

DefaultSharePointMode installs and configures the report server using default values, except the report server system property SharePointIntegratedMode is set to True. After installation finishes, the report server will not be operational until you install Windows SharePoint Services (WSS) 3.0 or Microsoft Office SharePoint Server (MOSS) 2007. Then, you must still join the report server to the SharePoint farm and configure integration settings for the SharePoint Web application.

RSSVCACCOUNT

<domain>\<user>

"NT AUTHORITY\NETWORK SERVICE"

"NT AUTHORITY\LOCAL SYSTEM"

"NT AUTHORITY\LOCAL SERVICE"

Yes

Specifies the service account of the report server service. If you specify a domain user account, the domain name must be under 254 characters and the user account name must be under 20 characters.

RSSVCPASSWORD

If you specify a built-in account, you can omit this value. Otherwise, specify the password of the domain user account.

Yes

Specify a strong password for the account. A strong password is at least 8 characters and includes a combination of upper and lower case alphanumeric characters and at least one symbol character.

RSSVCSTARTUPTYPE

Manual

Automatic

Disabled

No

Specifies the service startup type. The default is Automatic.

RSUPGRADEDATABASEACCOUNT

Database login for a remote report server database.

Required if the credentials you use to run Setup do not have sysadmin or database owner permissions on the report server database.

Specifies a SQL Server database login that is used one time during an upgrade operation to connect to the instance of the Database Engine that hosts the report server database. The account must have permission to update the report server database schema.

This value must be specified if you are upgrading a report server that uses a remote report server database to store application data, and the credentials you used to run Setup do not have sufficient permissions on the remote server.

RSUPGRADEPASSWORD

The password for the login or an empty string if the login does not have a password.

This value must be specified if RSUPGRADEDATABASEACCOUNT is specified.

Test and modify the following installation scripts to meet the needs of your organization.

To install Reporting Services server applications in files-only mode as the default instance using default values

  1. Insert the SQL Server installation media into the disk drive.

  2. Run the following command at the command prompt:

    Copy Code
    Setup /q /ACTION=install /FEATURES=RS /INSTANCENAME=MSSQLSERVER /RSSVCACCOUNT="NT AUTHORITY\NETWORK SERVICE"

If you intend to use default values, the command line can include minimal arguments. This example installs an un-configured report server in files-only mode without client tools, where the service account runs as Network Service. Notice that /RSINSTALLMODE is not specified. This is because files-only mode is the default installation mode and will be used if no other mode is specified.

Reporting Services requires an instance of the Database Engine to store application data. If you want to use an existing instance of the Database Engine for the report server databases, you must install Reporting Services in files-only mode so that you can specify a database server to use after installation is finished. For more information about files-only mode, see Files-Only Installation (Reporting Services).

To install Reporting Services, Database Engine Services, and client tools on a single computer in native mode in the default configuration

  1. Insert the SQL Server installation media into the disk drive.

  2. Run the following command at the command prompt:

    Copy Code
    setup /q /ACTION=install /FEATURES=SQL,RS,TOOLS /INSTANCENAME=MSSQLSERVER /SQLSYSADMINACCOUNTS="BUILTIN\ADMINISTRATORS" /RSSVCACCOUNT="Adventure-Works\RSUserAcct" /RSSVCPASSWORD="Som#Pas$w0rd" /SQLSVCACCOUNT="NT AUTHORITY\NETWORK SERVICE" /AGTSVCACCOUNT="NT AUTHORITY\NETWORK SERVICE" /RSSVCSTARTUPTYPE="Manual" /RSINSTALLMODE="DefaultNativeMode"

This script also installs Report Designer in Business Intelligence Development Studio and SQL Server Management Studio. To satisfy the requirements for default configuration, the Database Engine is also installed in the same instance as the report server. This script includes the full set of command line arguments for a report server installation, set to non-default values and fictional credentials. For more information about the default configuration modes, see Default Configuration for a Native Mode Installation (Reporting Services) and Default Configuration for SharePoint Integrated Mode (Reporting Services).

To upgrade a SQL Server 2005 report server that uses a remote report server database

  1. Insert the SQL Server installation media into the disk drive.

  2. Run the following command at the command prompt:

    Copy Code
    setup /q /ACTION=upgrade /INSTANCENAME=MSSQLSERVER /RSUPGRADEDATABASEACCOUNT="Adventure-Works\RSUserAcct" /RSUPGRADEPASSWORD ="Som#Pas$w0rd"

Setup components and features within the instance are upgraded to the new version; you cannot upgrade specific features within the same instance.

This script requires that you specify credentials for one-time connection to the remote Database Engine instance that hosts the report server database. You can omit RSUPGRADEDATABASEACCOUNT if you have sysadmin or database update permissions on the remote server. For more information about upgrading a report server, see Considerations for Upgrading Reporting Services.

To uninstall Reporting Services, Database Engine, and client tools

  1. Insert the SQL Server installation media into the disk drive.

  2. Run the following command at the command prompt:

    Copy Code
    setup /q /ACTION=uninstall /FEATURES=SQL,RS,Tools /INSTANCENAME=MSSQLSERVER

Installation Scripts for Integration Services

Integration Services is usually installed or upgraded at the same time as an instance of the SQL Server Database Engine. Although you can design and run Integration Services packages without an instance of the Database Engine, you cannot store SQL Server 2008 Integration Services packages in SQL Server unless an instance of the SQL Server 2008 Database Engine is available.

To install or upgrade Integration Services from the command prompt, specify "IS" as one of the values for the FEATURES command line option. Use the following options to configure the Integration Services service account:

Option Required? Description

ISSVCAccount

Required

The account the will run the Integration Services service. The recommended account is NT AUTHORITY\NETWORK SERVICE.

ISSVCPassword

Required

The password for the account specified as ISSVCAccount. When using the Network Service account, specify a blank password.

ISSVCStartupType

Optional

The startup type for the service. Valid values are Automatic, Manual, or Disabled. The default value is Automatic.
Note:
Integration Services is not instance-specific. You can only install a single instance of Integration Services on a computer. You connect to the service from management tools and client applications by using the name of the server on which the service is running.

Test and modify the following installation scripts to meet the needs of your organization.

To install Integration Services with the default settings along with an instance of the SQL Server Database Engine and the client tools.

  1. Insert the SQL Server installation media into the disk drive.

  2. Run the following command at the command prompt:

    Copy Code
    setup.exe /q /ACTION=install /FEATURES=SQL,IS,Tools /ISSVCACCOUNT="NT AUTHORITY\NETWORK SERVICE" /INSTANCENAME=MSSQLSERVER /SQLSVCACCOUNT="DomainName\UserName" /SQLSVCPASSWORD="StrongPassword" /SQLSYSADMINACCOUNTS="BUILTIN\ADMINISTRATORS" /AGTACCOUNT="DomainName\UserName" /AGTPASSWORD="StrongPassword"

Important   Do not use a blank password. Use a strong password.

Note:
For the default instance of the Database Engine, specify "MSSQLSERVER" for <InstanceName>. For a named instance, specify the instance name. In this example, the default instance is specified.

Parameters for SQL Server Installation

Use the parameters listed in the table below to develop command prompt installation scripts.

SQL Server Component Parameter Name Description Supported Values

Analysis Services

/ASBACKUPDIR

Specifies the directory for Analysis Services backup files.

Analysis Services

/ASCOLLATION

Specifies the collation setting for Analysis Services.

Analysis Services

/ASCONFIGDIR

Specifies the directory for Analysis Services configuration files.

Analysis Services

/ASDATADIR

Specifies the directory for Analysis Services data files.

Analysis Services

/ASLANGUAGE

Specifies the locale for Analysis Services.

Analysis Services

/ASLOGDIR

Specifies the directory for Analysis Services log files.

Analysis Services

/ASSVCACCOUNT

Specifies the account for the Analysis Services service.

Analysis Services

/ASSVCPASSWORD

Specifies the password for the Analysis Services service.

Analysis Services

/ASSVCSTARTUPTYPE

Specifies the startup mode for the Analysis Services service.

2=Automatic,

4=Disabled,

3=Manual

Analysis Services

/ASSYSADMINACCOUNTS

Specifies the administrator credentials for Analysis Services.

Analysis Services

/ASTEMPDIR

Directory for Analysis Services temporary files.

Analysis Services

/ASPROVIDERMSOLAP

Specifies whether the MSOLAP provider can run in-process.

1=enabled, 0=disabled

Database Engine

/ENABLERANU

Enables run-as credentials for SQL Server Expresss installations.

Database Engine

/INSTALLSQLDATADIR

Specifies the data directory for SQL Server data files.

1=enabled, 0=disabled

Database Engine

/REBUILDDATABASES

Database Engine

/SAPWD

Database Engine

/SECURITYMODE

/SECURITYMODE="SQL"

Database Engine

/SQLBACKUPDIR

Database Engine

/SQLCOLLATION

Database Engine

/SQLSVCACCOUNT

Database Engine

/SQLSVCPASSWORD

Database Engine

/SQLSVCStartuptype

Specifies the startup mode for the SQL Server service.

2=Automatic,

4=Disabled,

3=Manual

Database Engine

/SQLSYSADMINACCOUNTS

Use this parameter to provision users within SQL Server.

Database Engine

/SQLTEMPDBDIR

Database Engine

/SQLTEMPDBLOGDIR

Database Engine

/SQLUSERDBDIR

Database Engine

/SQLUSERDBLOGDIR

Integration Services

/ISSVCAccount

Specifies the account for Integration Services.

DomainName\UserName or System account

Integration Services

/ISSVCPassword

Specifies the Integration Services password.

Required only for a domain account.

Integration Services

/ISSVCStartupType

Specifies the startup type for the Integration Services service.

NLRegS extension of the DP

/NPENABLED

NLRegS extension of the DP

/TCPENABLED

Reporting Services

/RSInstallMode

Reporting Services

/RSSVCACCOUNT

Reporting Services

/RSSVCPASSWORD

Reporting Services

/RSSVCStartupType

Reporting Services

/RSUPGRADEDATABASEACCOUNT

Reporting Services

/RSUPGRADEPASSWORD

SQL Server Browser

/BROWSERSVCStartupType

Specifies the startup mode for SQL Server Browser service.

2=Automatic,

4=Disabled,

3=Manual

SQL Server Agent

/AGTSVCACCOUNT

Specifies the account for the SQL Server service.

DomainName\UserName or System account

SQL Server Agent

/AGTSVCPASSWORD

Specifies the SQL Server Agent password

Required only for a domain account.

SQL Server Agent

/AGTSVCSTARTUPTYPE

Specifies the startup mode for the SQL Server Agent service.

2=Automatic,

4=Disabled,

3=Manual

SQL Server Setup

/ACTION

Specifies an installation work flow.

Install, Uninstall, or Upgrade

SQL Server Setup

/ERRORREPORTING

Error reporting for SQL Server.

1=enabled; 0=disabled

SQL Server Setup

/FEATURES

Specifies components to install, uninstall, or upgrade.

SQL, SQLEngine, Replication, FullText, AS, RS, IS, TOOLS, BIDS, BOL

SQL Server Setup

/HELP, H, ?

Displays the usage options for installation parameters.

SQL Server Setup

/INDICATEPROGRESS

Specifies that the verbose Setup log file will be piped to the console.

SQL Server Setup

/INSTALLSHAREDDIR

Specifies a non-default installation dorectory for 64-bit components.

SQL Server Setup

/INSTALLSHAREDWOWDIR

Specifies a non-default installation dorectory for 32-bit components.

SQL Server Setup

/INSTANCEDIR

Specifies a non-default installation directory for shared components.

SQL Server Setup

/INSTANCEIDSUFFIX

Specifies a non-default value for an InstanceID.

SQL Server Setup

/INSTANCENAME

Specifies a non-default SQL Server instance name.

/InstanceName=MSSQLServer or /InstanceName=<Name of Named Instance>

SQL Server Setup

/Q

Specifies that Setup runs without any user interface.

SQL Server Setup

/SQMREPORTING

Specifies feature usage reporting for SQL Server.

1=enabled; 0=disabled

See Also

previous page start next page