Upgrade to a Different Edition of SQL Server (Setup)
Applies to: SQL Server - Windows only
SQL Server Setup supports edition upgrade among various editions of SQL Server. For information about supported edition upgrade paths, see Supported Version and Edition Upgrades. Before you initiate the edition upgrade of an instance of SQL Server, review the following articles:
Editions and supported features of SQL Server 2019
- Editions and supported features of SQL Server 2017
- Editions and supported features of SQL Server 2016
- Compute Capacity Limits by Edition of SQL Server
- Hardware and Software Requirements for Installing SQL Server
SQL Server on a failover cluster instance: Running edition upgrade on one of the nodes of SQL Server failover cluster instance is sufficient. This node can be either active or passive, and the engine does not bring the resources offline during the edition upgrade. After the edition upgrade it is required to either restart the SQL Server instance or failover to a different node.
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 permissions on the remote share.
For the SQL Server edition change to be activated, you must restart SQL Server services. This will result in application down time while services are offline.
To upgrade to a different edition of SQL Server
Insert the SQL Server installation media. From the root folder, double-click setup.exe or launch the SQL Server Installation Center from Configuration Tools. To install from a network share, locate the root folder on the share, and then double-click Setup.exe.
To upgrade an existing instance of SQL Server to a different edition, from the SQL Server Installation Center click Maintenance, and then select Edition Upgrade.
If Setup support files are required, SQL Server Setup installs them. If you are instructed to restart your computer, restart before you continue.
The System Configuration Checker runs a discovery operation on your computer. To continue, click OK.
On the Product Key page, select a radio button to indicate whether you are upgrading to a free edition of SQL Server, or whether you have a PID key for a production version of the product. For more information, see Editions and Components of SQL Server and Supported Version and Edition Upgrades.
On the License Terms page, read the license agreement, and then select the check box to accept the licensing terms and conditions. To continue, click Next. To end Setup, click Cancel.
On the Select Instance page, specify the instance of SQL Server to upgrade.
The Edition Upgrade Rules page validates your computer configuration before the edition upgrade operation begins.
The Ready to Upgrade Edition page shows a tree view of installation options that were specified during Setup. To continue, click Upgrade.
During the edition upgrade process, the services need to be restarted to pick up the new setting. After edition upgrade, the Complete page provides a link to the summary log file for the edition upgrade. To close the wizard, click Close.
The Complete page provides a link to the summary log file for the installation and other important notes.
If you are instructed to restart the computer, do so now. It is important to read the message from the Installation Wizard when you are done with Setup. For information about Setup log files, see View and Read SQL Server Setup Log Files.
If you upgraded from SQL Server Express, you must perform additional steps before you can use your upgraded instance of SQL Server:
Enable the SQL Server Agent service in Windows SCM.
Provision the SQL Server Agent service account by using SQL Server Configuration Manager.
In addition to the steps above, you may need to do the following if you upgraded from SQL Server Express:
Users that were provisioned in SQL Server Express remain provisioned after the upgrade. Specifically, the BUILTIN\Users group remains provisioned. Disable, remove, or reprovision these accounts as needed. For more information, see Configure Windows Service Accounts and Permissions.
Sizes and recovery mode for the tempdb and model system databases remain unchanged after the upgrade. Reconfigure these settings as needed. For more information, see Back Up and Restore of System Databases (SQL Server).
Template databases remain on the computer after the upgrade.
If the procedure fails on Engine_SqlEngineHealthCheck rule, then you can use the command line installation option to skip this specific rule to allow the upgrade process to complete successfully. To skip checking this rule, open a command prompt, change to the path that contains SQL Server Setup (Setup.exe). Then, type the following command:
setup.exe /q /ACTION=editionupgrade /InstanceName=MSSQLSERVER /PID=<appropriatePid> /SkipRules=Engine_SqlEngineHealthCheck
Submit and view feedback for