Install, configure, or uninstall SQL Server on Windows from the command prompt

Applies to: SQL Server - Windows only

Before you run SQL Server Setup, review Plan 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.

To install or configure your SQL Server instance from the command prompt, open an administrative command prompt and navigate to where setup.exe is located within the SQL Server Setup media. Run the setup.exe command, along with the required and optional parameters that accomplish what you're trying to do:

C:\SQLMedia\SQLServer2022> setup.exe /[Option] /[Option] = {value}

The following example installs the SQL Server Database Engine, SQL Server Analysis Services, SQL Server, and Integration Services in quiet mode:

C:\SQLMedia\SQLServer2022> setup.exe /Q /IACCEPTSQLSERVERLICENSETERMS /ACTION="install"
/PID="AAAAA-BBBBB-CCCCC-DDDDD-EEEEE" /FEATURES=SQL,AS,IS
/INSTANCENAME=MSSQLSERVER /SQLSVCACCOUNT="MyDomain\MyAccount"
/SQLSVCPASSWORD="************" /SQLSYSADMINACCOUNTS="MyDomain\MyAccount "
/AGTSVCACCOUNT="MyDomain\MyAccount" /AGTSVCPASSWORD="************"
/ASSVCACCOUNT="MyDomain\MyAccount" /ASSVCPASSWORD="************"
/ISSVCACCOUNT="MyDomain\MyAccount" /ISSVCPASSWORD="************"
/ASSYSADMINACCOUNTS="MyDomain\MyAccount"

To view a list of all possible commands within the console, run the executable with the /help flag:

C:\SQLMedia\SQLServer2022> setup.exe /help

The rest of the article provides a detailed description of the available parameters.

Regardless of the installation method, you're required to confirm acceptance of the software license terms as an individual or on behalf of an entity, unless your use of the software is governed by a separate agreement such as a Microsoft volume licensing agreement or a third-party agreement with an ISV or OEM.

The license terms are displayed for review and acceptance in the Setup user interface. Unattended installations (using the /Q or /QS parameters) must include the /IACCEPTSQLSERVERLICENSETERMS parameter. You can review the license terms separately at Microsoft Software License Terms.

For SQL Server 2022 (16.x) and later versions, read the Microsoft SQL Server Software License Terms at aka.ms/useterms.

Depending on how you received the software (for example, through Microsoft volume licensing), your use of the software can be subject to additional terms and conditions.

Command line installation is supported in the following scenarios:

• Installing, upgrading, or removing an instance and shared components of SQL Server on a local computer by using syntax and parameters specified at the command prompt.
• Installing, upgrading, or removing a failover cluster instance.
• Upgrading from one SQL Server edition to another edition of SQL Server.
• Installing an instance of SQL Server on a local computer by using 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.

Proper use of setup parameters

Use the following guidelines to develop installation commands that have correct syntax:

Parameter options

The following sections provide parameters to develop command-line installation scripts for install, update, and repair scenarios. Parameters can take different values depending on the chosen scenario.

Parameters that are listed for a SQL Server Database Engine component are specific to that component. SQL Server Agent and SQL Server Browser parameters are applicable when you install the SQL Server Database Engine.

• Installation parameters
• SysPrep parameters
• Upgrade parameters
• Repair parameters
• Rebuild system database parameters
• Uninstall parameters
• Failover cluster parameters
• Service account parameters
• Feature parameters
• Role parameters
• Control failover behavior using the /FAILOVERCLUSTERROLLOWNERSHIP parameter
• Instance ID or InstanceID configuration

Installation parameters

Use the parameters in the following table to develop command-line scripts for installing a new instance of SQL Server.

Sample syntax

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

setup.exe /q /ACTION=Install /FEATURES=SQL /INSTANCENAME=MSSQLSERVER /SQLSVCACCOUNT="<DomainName\UserName>" /SQLSVCPASSWORD="<StrongPassword>" /SQLSYSADMINACCOUNTS="<DomainName\UserName>" /AGTSVCACCOUNT="NT AUTHORITY\NETWORK SERVICE" /SQLSVCINSTANTFILEINIT="True" /IACCEPTSQLSERVERLICENSETERMS

Install and connect to Azure

Beginning with SQL Server 2022 (16.x), you can install the Azure Arc agent with the Azure extension for SQL Server using SQL Server setup. When you install the Azure Arc agent and SQL Server extension, you automatically Arc-enable all the instances on the host, which registers the SQL Server instances as resources in Azure and make them eligible to have additional Azure management services attached.

Beginning with SQL Server 2025 (17.x) Preview, you can install the Azure extension for SQL Server using SQL Server setup on Azure virtual machines. When you install the Azure SQL Server extension, you automatically register with SQL Server on Azure VM service and enable the additional management capabilities that the service provides.

The following example installs a SQL Server instance, the Azure Arc agent (if not on an Azure VM), and the Azure extension for SQL Server so that the SQL Server instance is connected to Azure after installation. Before you run the example, replace the information in angle brackets ( < ... > ) with your information.

setup.exe /qs /ACTION=Install /FEATURES=SQLEngine,AZUREEXTENSION /INSTANCENAME=<instance name> /SQLSYSADMINACCOUNTS="<sysadmin account>" /IACCEPTSQLSERVERLICENSETERMS /AZURESUBSCRIPTIONID="<Azure subscription>" /AZURETENANTID="<Azure tenant ID>" /AZURERESOURCEGROUP="<resource group name>" /AZURESERVICEPRINCIPAL="<service principal>" /AZURESERVICEPRINCIPALSECRET="<secret>" /AZUREREGION=<Azure region>

The following example installs the Azure Arc agent and Azure extension for SQL Server to manage all the existing SQL Server instances that are installed.

setup.exe /qs /ACTION=Install /FEATURES=AZUREEXTENSION /IACCEPTSQLSERVERLICENSETERMS /AZURESUBSCRIPTIONID="<Azure subscription>" /AZURETENANTID="<Azure tenant ID>" /AZURERESOURCEGROUP="<resource group name>" /AZURESERVICEPRINCIPAL="<service principal>" /AZURESERVICEPRINCIPALSECRET="<secret>" /AZUREREGION=<Azure region>

The following example shows how to remove the Azure extension for SQL Server using SQL Server setup:

setup.exe /qs /ACTION=Uninstall /FEATURES=AZUREEXTENSION /IACCEPTSQLSERVERLICENSETERMS

For more information about connecting to Azure Arc or SQL Server on Azure VM, see:

• SQL Server enabled by Azure Arc
• Connect your SQL Server to Azure Arc
• What is SQL Server on Azure Windows Virtual Machines?
• Register Windows SQL Server VM with SQL IaaS Agent extension

SysPrep parameters

For more information about SQL Server SysPrep, see Install SQL Server with SysPrep.

Prepare image parameters

Use the parameters in the following table to develop command-line scripts for preparing an instance of SQL Server without configuring it.

¹ Distributed Replay, SDK, and SNAC aren't available in SQL Server 2022 (16.x).

Sample syntax

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

setup.exe /q /ACTION=PrepareImage /FEATURES=SQL,RS /InstanceID =<MYINST> /IACCEPTSQLSERVERLICENSETERMS

Complete image parameters

Use the parameters in the following table to develop command-line scripts for completing and configuring a prepared instance of SQL Server.

Sample syntax

To complete a prepared, stand-alone instance that includes SQL Server Database Engine, Replication, and Full-Text Search components.

setup.exe /q /ACTION=CompleteImage /INSTANCENAME=MYNEWINST /INSTANCEID=<MYINST> /SQLSVCACCOUNT="<DomainName\UserName>" /SQLSVCPASSWORD="<StrongPassword>" /SQLSYSADMINACCOUNTS="<DomainName\UserName>" /AGTSVCACCOUNT="NT AUTHORITY\NETWORK SERVICE" /IACCEPTSQLSERVERLICENSETERMS

Upgrade parameters

Use the parameters in the following table to develop command-line scripts for upgrade.

Sample syntax

To upgrade an existing instance or failover cluster node from a previous SQL Server Database Engine version,

setup.exe /q /ACTION=upgrade /INSTANCEID = <INSTANCEID>/INSTANCENAME=MSSQLSERVER /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" /IACCEPTSQLSERVERLICENSETERMS

Repair parameters

Use the parameters in the following table to develop command-line scripts for repair.

Sample syntax

Repair an instance and shared components.

setup.exe /q /ACTION=Repair /INSTANCENAME=<instancename>

Rebuild system database parameters

Use the parameters in the following table to develop command-line scripts for rebuilding the master, model, msdb, and tempdb system databases. For more information, see Rebuild system databases.

Uninstall parameters

Use the parameters in the following table to develop command-line scripts for uninstallation.

Sample syntax

Use the following command to uninstall an existing instance of SQL Server from the command prompt.

setup.exe /Action=Uninstall /FEATURES=SQL,AS,RS,IS,Tools /INSTANCENAME=MSSQLSERVER

To remove a named instance, specify the name of the instance instead of MSSQLSERVER in the previous example.

To uninstall an existing SQL Server update from command prompt, you can find the complete uninstall command for a specific component in the Windows registry, using the following registry path. Look for the "UninstallString" key.

The following example shows the path for a specific KB update.

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB5014356

You can get the uninstall command from "UninstallString" in this registry key. For example:

C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Update Cache\KB5014356\GDR\setup.exe" /Action=RemovePatch /AllInstances

Failover cluster parameters

Before you install a SQL Server Database Engine failover cluster instance, review the following articles:

• Hardware and software requirements for SQL Server 2022

• Security considerations for a SQL Server installation

• Before Installing Failover Clustering

• Always On failover cluster instances (SQL Server)

  Important

  All failover cluster installation commands require an underlying Windows cluster. All the nodes that are part of a SQL Server Database Engine failover cluster must be part of the same Windows cluster.

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

Integrated install failover cluster parameters

Use the parameters in the following table to develop command-line scripts for failover cluster installation.

For more information about Integrated Installation, see Always On failover cluster instances (SQL Server).

We recommend that you use Service SID instead of domain groups.

Additional notes

The Database Engine and Analysis Services are the only components that are cluster-aware. Other features aren't cluster-aware and don't have high availability through failover.

Sample syntax

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

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 - for example, 'Disk S:'" /FAILOVERCLUSTERNETWORKNAME="<Insert Network Name>" /FAILOVERCLUSTERIPADDRESSES="IPv4;xx.xxx.xx.xx;Cluster Network;xxx.xxx.xxx.x" /FAILOVERCLUSTERGROUP="MSSQLSERVER" /Features=AS,SQL /ASSVCACCOUNT="<DomainName\UserName>" /ASSVCPASSWORD="xxxxxxxxxxx" /AGTSVCACCOUNT="<DomainName\UserName>" /AGTSVCPASSWORD="xxxxxxxxxxx" /INSTALLSQLDATADIR="<Drive>:\<Path>\MSSQLSERVER" /SQLCOLLATION="SQL_Latin1_General_CP1_CS_AS" /SQLSVCACCOUNT="<DomainName\UserName>" /SQLSVCPASSWORD="xxxxxxxxxxx" /SQLSYSADMINACCOUNTS="<DomainName\UserName> /IACCEPTSQLSERVERLICENSETERMS

Prepare failover cluster parameters

Use the parameters in the following table to develop command-line scripts for failover cluster prepare. This is the first step in advanced cluster installation, where you have to prepare the failover cluster instances on all the nodes of the failover cluster. For more information, see Always On failover cluster instances (SQL Server).

We recommend that you use Service SID instead of domain groups.

Sample syntax

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

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

setup.exe /q /ACTION=PrepareFailoverCluster /InstanceName=MSSQLSERVER /Features=AS,SQL /INDICATEPROGRESS /ASSVCACCOUNT="<DomainName\UserName>" /ASSVCPASSWORD="xxxxxxxxxxx" /SQLSVCACCOUNT="<DomainName\UserName>" /SQLSVCPASSWORD="xxxxxxxxxxx" /AGTSVCACCOUNT="<DomainName\UserName>" /AGTSVCPASSWORD="xxxxxxxxxxx" /IACCEPTSQLSERVERLICENSETERMS

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

setup.exe /q /ACTION=PrepareFailoverCluster /InstanceName="<Insert Instance name>" /Features=AS,SQL /INDICATEPROGRESS /ASSVCACCOUNT="<DomainName\UserName>" /ASSVCPASSWORD="xxxxxxxxxxx" /SQLSVCACCOUNT="<DomainName\UserName>" /SQLSVCPASSWORD="xxxxxxxxxxx" /AGTSVCACCOUNT="<DomainName\UserName>" /AGTSVCPASSWORD="xxxxxxxxxxx" /IACCEPTSQLSERVERLICENSETERMS

For SQL Server 2022 (16.x) and later versions, read the Microsoft SQL Server Software License Terms at aka.ms/useterms.

Complete failover cluster parameters

Use the parameters in the following table to develop command-line scripts for failover cluster complete. This is the second step in the advanced failover cluster install option. After you have run prepare on all the failover cluster nodes, you run this command on the node that owns the shared disks. For more information, see Always On failover cluster instances (SQL Server).

Sample syntax

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

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

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;Cluster Network;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:

setup.exe /q /ACTION=CompleteFailoverCluster /InstanceName="<Insert Instance Name>" /INDICATEPROGRESS /ASSYSADMINACCOUNTS="<DomainName\UserName>" /ASDATADIR=<Drive>:\INSTANCE\Data /ASLOGDIR=<drive>:\INSTANCE\Log /ASBACKUPDIR=<Drive>:\INSTANCE\Backup /ASCONFIGDIR=<Drive>:\INSTANCE\Config /ASTEMPDIR=<Drive>:\INSTANCE\Temp /FAILOVERCLUSTERDISKS="<Cluster Disk Resource Name - for example, 'Disk S:'>" /FAILOVERCLUSTERNETWORKNAME="CompNamedFOI" /FAILOVERCLUSTERIPADDRESSES="IPv4;xx.xxx.xx.xx;ClusterNetwork1;xxx.xxx.xxx.x" /FAILOVERCLUSTERGROUP="<Insert New Group Name>" /INSTALLSQLDATADIR="<Drive>:\<Path>\MSSQLSERVER_INSTANCE" /SQLCOLLATION="SQL_Latin1_General_CP1_CS_AS" /SQLSYSADMINACCOUNTS="<DomainName\Username>"

Upgrade failover cluster parameters

Use the parameters in the following table to develop command-line scripts for failover cluster upgrade. For more information, see Upgrade a SQL Server Database Engine failover Cluster Instance (Setup) and Always On failover cluster instances (SQL Server).

Add node parameters

Use the parameters in the following table to develop command-line scripts for AddNode.

Additional notes

The Database Engine and Analysis Services are the only components that are cluster-aware. Other features aren't cluster-aware and don't have high availability through failover.

Sample syntax

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

setup.exe /q /ACTION=AddNode /INSTANCENAME="<Insert Instance Name>" /SQLSVCACCOUNT="<SQL account that is used on other nodes>" /SQLSVCPASSWORD="<password for SQL account>" /AGTSVCACCOUNT="<SQL Server Agent account that is used on other nodes>", /AGTSVCPASSWORD="<SQL Server Agent account password>" /ASSVCACCOUNT="<AS account that is used on other nodes>" /ASSVCPASSWORD="<password for AS account>" /INDICATEPROGRESS /IACCEPTSQLSERVERLICENSETERMS /FAILOVERCLUSTERIPADDRESSES="IPv4;xx.xxx.xx.xx;ClusterNetwork1;xxx.xxx.xxx.x" /CONFIRMIPDEPENDENCYCHANGE=0

Remove node parameters

Use the parameters in the following table to develop command-line scripts for RemoveNode. To uninstall a failover cluster, you must run RemoveNode on each failover cluster node. For more information, see Always On failover cluster instances (SQL Server).

Sample syntax

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

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

Service account parameters

You can configure the SQL Server services by using a built-in account, local account, or domain account.

For more information about service account configuration, see Configure Windows service accounts and permissions.

Feature parameters

To install specific features, use the /FEATURES parameter and specify the parent feature or feature values in the following table.

For a list of features supported by the editions of SQL Server on Windows, see:

• Editions and supported features of SQL Server 2025 Preview
• Editions and supported features of SQL Server 2022
• Editions and supported features of SQL Server 2019
• Editions and supported features of SQL Server 2017
• Editions and supported features of SQL Server 2016

¹ SQL Server Management Studio (SSMS) is now in a standalone installer that is separate from the SQL Server installer. For details, see Install SQL Server Management Studio.

Feature parameter examples

Role parameters

The setup role or /ROLE parameter is used to install a preconfigured selection of features. The SSAS roles install an SSAS instance in either an existing SharePoint farm, or a new unconfigured farm. Two setup roles are provided to support each scenario. You can only choose one setup role to install at a time. If you choose a setup role, Setup installs the features and components that belong to the role. You can't vary the features and components that are designated for that role. For more information about how to use the feature role parameter, see Install Power Pivot from the Command Prompt.

The AllFeatures_WithDefaults role is the default behavior for editions of SQL Server Express and reduces the number of dialog boxes presented to the user. It can be specified from the command line when installing a SQL Server edition that isn't SQL Server Express.

Control failover behavior using the /FAILOVERCLUSTERROLLOWNERSHIP parameter

To upgrade a SQL Server Database Engine failover cluster, you must run the Setup on one failover cluster node at a time, starting with the passive nodes. Setup determines when to fail over to the upgraded node, depending on the total number of nodes in the failover cluster instance, and the number of nodes that have already been upgraded. When half of the nodes or more have already been upgraded, Setup by default causes a failover to an upgraded node.

To control the failover behavior of cluster nodes during the upgrade process, run the upgrade operation at the command line and use the /FAILOVERCLUSTERROLLOWNERSHIP parameter to control the failover behavior before the upgrade operation takes the node offline. Use of this parameter is as follows:

• /FAILOVERCLUSTERROLLOWNERSHIP=0 doesn't roll cluster ownership (move group) to upgraded nodes, and doesn't add this node to the list of possible owners of the SQL Server cluster at the end of upgrade.

• /FAILOVERCLUSTERROLLOWNERSHIP=1 rolls cluster ownership (move group) to upgraded nodes, and adds 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's used if this parameter isn't specified. This setting indicates that SQL Server Setup manages cluster ownership (move group) as needed.

Instance ID or InstanceID configuration

The Instance ID or /InstanceID parameter is used for specifying where you can install the instance components and the registry path of the instance. The value of INSTANCEID is a string and should be unique.

• SQL Instance ID: MSSQLxx.<INSTANCEID>
• AS Instance ID: MSASxx.<INSTANCEID>
• RS Instance ID: MSRSxx.<INSTANCEID>

The instance-aware components are installed to the following locations:

• %Program Files%\Microsoft SQL Server\<SQLInstanceID>
• %Program Files%\Microsoft SQL Server\<ASInstanceID>
• %Program Files%\Microsoft SQL Server\<RSInstanceID>

Related content

• Slipstream installation for SQL Server
• Install SQL Server from the Installation Wizard (Setup)
• Install a SQL Server failover cluster
• Install SQL Server Business Intelligence Features