Skip to content

upgrade-to-a-different-edition-of-sql-server-setup.md

Latest commit

 

History

History
84 lines (53 loc) · 7 KB

upgrade-to-a-different-edition-of-sql-server-setup.md

File metadata and controls

84 lines (53 loc) · 7 KB
title Upgrade to a Different Edition of SQL Server 2016 (Setup) | Microsoft Docs
ms.custom
ms.date 03/14/2017
ms.prod sql-server-2016
ms.reviewer
ms.suite
ms.technology
setup-install
ms.tgt_pltfrm
ms.topic article
ms.assetid 31d16820-d126-4c57-82cc-27701e4091bc
caps.latest.revision 27
author MikeRayMSFT
ms.author mikeray
manager jhubbard

Upgrade to a Different Edition of SQL Server (Setup)

[!INCLUDEssNoVersion] Setup supports edition upgrade among various editions of [!INCLUDEssCurrent]. For information about supported edition upgrade paths, see Supported Version and Edition Upgrades. Before you initiate the edition upgrade of an instance of [!INCLUDEssCurrent], review the following topics:

Note

[!INCLUDEssNoVersion] in a clustered environment: Running edition upgrade on one of the nodes of [!INCLUDEssNoVersion] cluster 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 [!INCLUDEssNoVersion] instance or failover to a different node.

Prerequisites

For local installations, you must run Setup as an administrator. If you install [!INCLUDEssNoVersion] from a remote share, you must use a domain account that has read permissions on the remote share.

Important

For the [!INCLUDEssNoVersion] edition change to be activated, you must restart [!INCLUDEssNoVersion] services. This will result in application down time while services are offline.

Procedure

To upgrade to a different edition of [!INCLUDEssCurrent]

  1. Insert the [!INCLUDEssNoVersion] installation media. From the root folder, double-click setup.exe or launch the [!INCLUDEssNoVersion] Installation Center from Configuration Tools. To install from a network share, locate the root folder on the share, and then double-click Setup.exe.

  2. To upgrade an existing instance of [!INCLUDEssCurrent] to a different edition, from the [!INCLUDEssNoVersion] Installation Center click Maintenance, and then select Edition Upgrade.

  3. If Setup support files are required, [!INCLUDEssNoVersion] Setup installs them. If you are instructed to restart your computer, restart before you continue.

  4. The System Configuration Checker runs a discovery operation on your computer. To continue, click OK.

  5. On the Product Key page, select a radio button to indicate whether you are upgrading to a free edition of [!INCLUDEssNoVersion], or whether you have a PID key for a production version of the product. For more information, see Editions and Components of SQL Server 2016 and Supported Version and Edition Upgrades.

  6. 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.

  7. On the Select Instance page, specify the instance of [!INCLUDEssNoVersion] to upgrade.

  8. The Edition Upgrade Rules page validates your computer configuration before the edition upgrade operation begins.

  9. The Ready to Upgrade Edition page shows a tree view of installation options that were specified during Setup. To continue, click Upgrade.

  10. 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.

  11. The Complete page provides a link to the summary log file for the installation and other important notes.

  12. 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.

  13. If you upgraded from [!INCLUDEssExpress], you must perform additional steps before you can use your upgraded instance of [!INCLUDEssNoVersion]:

    • Enable the [!INCLUDEssNoVersion] Agent service in Windows SCM.

    • Provision the [!INCLUDEssNoVersion] Agent service account by using [!INCLUDEssNoVersion] Configuration Manager.

In addition to the steps above, you may need to do the following if you upgraded from [!INCLUDEssExpress]:

  • Users that were provisioned in [!INCLUDEssExpress] 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.

See Also

Upgrade to SQL Server 2016
Backward Compatibility_deleted