| title | Supported Version and Edition Upgrades | Microsoft Docs | ||||
|---|---|---|---|---|---|
| ms.custom | |||||
| ms.date | 06/27/2016 | ||||
| ms.prod | sql | ||||
| ms.reviewer | |||||
| ms.technology | install | ||||
| ms.topic | conceptual | ||||
| helpviewer_keywords |
|
||||
| ms.assetid | 702359c4-6ca9-42a8-860c-a95a802898a1 | ||||
| author | MashaMSFT | ||||
| ms.author | mathoma | ||||
| monikerRange | >=sql-server-2016||=sqlallproducts-allversions |
[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md-winonly]
You can upgrade from [!INCLUDEssKatmai], [!INCLUDEssKilimanjaro], [!INCLUDEssSQL11], and [!INCLUDEssSQL14]. This article lists the supported upgrade paths from these [!INCLUDEssNoVersion] versions, and the supported edition upgrades for [!INCLUDEsssql15-md].
-
Before upgrading from one edition of [!INCLUDEsssql15-md] to another, verify that the functionality you are currently using is supported in the edition to which you are moving.
-
Before upgrading [!INCLUDEssNoVersion], enable Windows Authentication for [!INCLUDEssNoVersion] Agent and verify the default configuration: that the [!INCLUDEssNoVersion] Agent service account is a member of the [!INCLUDEssNoVersion] sysadmin group.
-
To upgrade to [!INCLUDEsssql15-md], you must be running a supported operating system. For more information, see Hardware and Software Requirements for Installing SQL Server 2016.
-
Upgrade will be blocked if there is a pending restart.
-
Upgrade will be blocked if the Windows Installer service is not running.
-
Cross-version instances of [!INCLUDEsssql15-md] are not supported. Version numbers of the [!INCLUDEssDE], [!INCLUDEssASnoversion], and [!INCLUDEssRSnoversion] components must be the same in an instance of [!INCLUDEsssql15-md].
-
[!INCLUDEsssql15-md] is only available for 64-bit platforms. Cross-platform upgrade is not supported. You cannot upgrade a 32-bit instance of [!INCLUDEssNoVersion] to native 64-bit using [!INCLUDEssNoVersion] Setup. However, you can back up or detach databases from a 32-bit instance of [!INCLUDEssNoVersion], and then restore or attach them to a new instance of [!INCLUDEssNoVersion] (64-bit) if the databases are not published in replication. You must re-create any logins and other user objects in master, msdb, and model system databases.
-
You cannot add new features during the upgrade of your existing instance of [!INCLUDEssNoVersion]. After you upgrade an instance of [!INCLUDEssNoVersion] to [!INCLUDEsssql15-md], you can add features by using the [!INCLUDEsssql15-md] Setup. For more information, see Add Features to an Instance of SQL Server 2016 (Setup).
-
Failover Clusters are not supported in WOW mode.
-
Upgrade from an Evaluation edition of a previous [!INCLUDEssNoVersion] version is not supported.
-
When upgrading from RC1 or previous versions of SQL Server 2016 to RC3 or later versions, PolyBase must be uninstalled before the upgrade and reinstalled after the upgrade.
Upgrades from Earlier Versions to [!INCLUDEsssql15-md]
SQL Server 2016 supports upgrade from the following versions of SQL Server:
- [!INCLUDEssKatmai] SP4 or later
- [!INCLUDEssKilimanjaro] SP3 or later
- [!INCLUDEssSQL11] SP2 or later
- [!INCLUDEssSQL14] or later
Note
To upgrade databases on [!INCLUDEssVersion2005] see Support for 2005.
The table below lists the supported upgrade scenarios from earlier versions of [!INCLUDEssNoVersion] to [!INCLUDEsssql15-md].
| Upgrade from | Supported upgrade path |
|---|---|
| [!INCLUDEssKatmai] SP4 Enterprise | [!INCLUDEsssql15-md] Enterprise |
| [!INCLUDEssKatmai] SP4 Developer | [!INCLUDEsssql15-md] Developer |
| [!INCLUDEssKatmai] SP4 Standard | [!INCLUDEsssql15-md] Enterprise [!INCLUDEsssql15-md] Standard |
| [!INCLUDEssKatmai] SP4 Small Business | [!INCLUDEsssql15-md] Standard |
| [!INCLUDEssKatmai] SP4 Web | [!INCLUDEsssql15-md] Enterprise [!INCLUDEsssql15-md] Standard [!INCLUDEsssql15-md] Web |
| [!INCLUDEssKatmai] SP4 Workgroup | [!INCLUDEsssql15-md] Enterprise [!INCLUDEsssql15-md] Standard |
| [!INCLUDEssKatmai] SP4 Express | [!INCLUDEsssql15-md] Enterprise [!INCLUDEsssql15-md] Standard [!INCLUDEsssql15-md] Web [!INCLUDEsssql15-md] Express |
| [!INCLUDEssKilimanjaro] SP3 Datacenter | [!INCLUDEsssql15-md] Enterprise |
| [!INCLUDEssKilimanjaro] SP3 Enterprise | [!INCLUDEsssql15-md] Enterprise |
| [!INCLUDEssKilimanjaro] SP3 Developer | [!INCLUDEsssql15-md] Developer |
| [!INCLUDEssKilimanjaro] SP3 Small Business | [!INCLUDEsssql15-md] Standard |
| [!INCLUDEssKilimanjaro] SP3 Standard | [!INCLUDEsssql15-md] Enterprise [!INCLUDEsssql15-md] Standard |
| [!INCLUDEssKilimanjaro] SP3 Web | [!INCLUDEsssql15-md] Enterprise [!INCLUDEsssql15-md] Standard [!INCLUDEsssql15-md] Web |
| [!INCLUDEssKilimanjaro] SP3 Workgroup | [!INCLUDEsssql15-md] Enterprise [!INCLUDEsssql15-md] Standard |
| [!INCLUDEssKilimanjaro] SP3 Express | [!INCLUDEsssql15-md] Enterprise [!INCLUDEsssql15-md] Standard [!INCLUDEsssql15-md] Web [!INCLUDEsssql15-md] Express |
| [!INCLUDEssSQL11] SP2 Enterprise | [!INCLUDEsssql15-md] Enterprise |
| [!INCLUDEssSQL11] SP2 Developer | [!INCLUDEsssql15-md] Developer [!INCLUDEsssql15-md] Standard [!INCLUDEsssql15-md] Web [!INCLUDEsssql15-md] Enterprise |
| [!INCLUDEssSQL11] SP2 Standard | [!INCLUDEsssql15-md] Enterprise [!INCLUDEsssql15-md] Standard |
| [!INCLUDEssSQL11] SP1 Web | [!INCLUDEsssql15-md] Enterprise [!INCLUDEsssql15-md] Standard [!INCLUDEsssql15-md] Web |
| [!INCLUDEssSQL11] SP2 Express | [!INCLUDEsssql15-md] Enterprise [!INCLUDEsssql15-md] Standard [!INCLUDEsssql15-md] Web [!INCLUDEsssql15-md] Express |
| [!INCLUDEssSQL11] SP2 Business Intelligence | [!INCLUDEsssql15-md] Enterprise |
| [!INCLUDEssSQL11] SP2 Evaluation | [!INCLUDEsssql15-md] Evaluation [!INCLUDEsssql15-md] Enterprise [!INCLUDEsssql15-md] Standard [!INCLUDEsssql15-md] Web [!INCLUDEsssql15-md] Developer |
| [!INCLUDEssSQL14] Enterprise | [!INCLUDEsssql15-md] Enterprise |
| [!INCLUDEssSQL14] Developer | [!INCLUDEsssql15-md] Developer [!INCLUDEsssql15-md] Standard [!INCLUDEsssql15-md] Web [!INCLUDEsssql15-md] Enterprise |
| [!INCLUDEssSQL14] Standard | [!INCLUDEsssql15-md] Enterprise [!INCLUDEsssql15-md] Standard |
| [!INCLUDEssSQL14] Web | [!INCLUDEsssql15-md] Enterprise [!INCLUDEsssql15-md] Standard [!INCLUDEsssql15-md] Web |
| [!INCLUDEssSQL14] Express | [!INCLUDEsssql15-md] Enterprise [!INCLUDEsssql15-md] Standard [!INCLUDEsssql15-md] Web [!INCLUDEsssql15-md] Express [!INCLUDEsssql15-md] Developer |
| [!INCLUDEssSQL14] Business Intelligence | [!INCLUDEsssql15-md] Enterprise |
| [!INCLUDEssSQL14] Evaluation | [!INCLUDEsssql15-md] Evaluation [!INCLUDEsssql15-md] Enterprise [!INCLUDEsssql15-md] Standard [!INCLUDEsssql15-md] Web [!INCLUDEsssql15-md] Developer |
| [!INCLUDEssSQL15_md] release candidate* | [!INCLUDEsssql15-md] Enterprise |
| [!INCLUDEssSQL15_md] Developer | [!INCLUDEsssql15-md] Enterprise |
* Microsoft support to upgrade from release candidate software is specifically for customers who participated in the Technology Adoption Program (TAP).
[!INCLUDEsssql15-md] Support for [!INCLUDEssVersion2005]
This section discusses [!INCLUDEsssql15-md] support for [!INCLUDEssVersion2005]. In [!INCLUDEsssql15-md], you will be able to do the following:
-
Attach a [!INCLUDEssVersion2005] database (mdf/ldf files) to [!INCLUDEsssql15-md] instance of database engine.
-
Restore a [!INCLUDEssVersion2005] database to [!INCLUDEsssql15-md] instance of database engine from a backup.
-
Back up a [!INCLUDEssASversion2005] cube and restoring on [!INCLUDEsssql15-md].
Note
When a [!INCLUDEssVersion2005] database is upgraded to [!INCLUDEsssql15-md], the database compatibility level will be changed from 90 to 100. In [!INCLUDEsssql15-md], valid values for the database compatibility level are 100, 110, 120, and 130. ALTER DATABASE Compatibility Level (Transact-SQL) discusses how the compatibility level change could affect [!INCLUDEssNoVersion] applications.
Any scenarios not specified in the list above are not supported, including but not limited to the following:
-
Installing [!INCLUDEssVersion2005] and [!INCLUDEsssql15-md] on same computer (side by side).
-
Using a [!INCLUDEssVersion2005] instance as a member of the replication topology that involves a [!INCLUDEsssql15-md] instance.
-
Configuring database mirroring between [!INCLUDEsssql15-md] and [!INCLUDEssVersion2005] instances.
-
Backing up the transaction log with log shipping between [!INCLUDEsssql15-md] and [!INCLUDEssVersion2005] instances.
-
Configuring linked servers between [!INCLUDEsssql15-md] and [!INCLUDEssVersion2005] instances.
-
Managing a [!INCLUDEssVersion2005] instance from a [!INCLUDEsssql15-md] Management Studio.
-
Attaching a [!INCLUDEssASversion2005] cube in [!INCLUDEsssql15-md] Management Studio.
-
Connecting to [!INCLUDEssISversion2005] from [!INCLUDEsssql15-md] Management Studio.
-
Managing a [!INCLUDEssISversion2005] service from [!INCLUDEsssql15-md] Management Studio.
-
Support for [!INCLUDEssVersion2005] third party custom Integration Services components, such as execute and upgrade.
[!INCLUDEsssql15-md] Edition Upgrade
The following table lists the supported edition upgrade scenarios in [!INCLUDEsssql15-md].
For step-by-step instructions on how to perform an edition upgrade, see Upgrade to a Different Edition of SQL Server 2016 (Setup).
| Upgrade From | Upgrade To |
|---|---|
| [!INCLUDEsssql15-md] Enterprise (Server+CAL and Core)** | [!INCLUDEsssql15-md] Enterprise |
| [!INCLUDEsssql15-md] Evaluation Enterprise** | [!INCLUDEsssql15-md] Enterprise (Server+CAL or Core License) [!INCLUDEsssql15-md] Standard [!INCLUDEsssql15-md] Developer [!INCLUDEsssql15-md] Web Upgrading from Evaluation (a free edition) to any of the paid editions is supported for stand-alone installations, but is not supported for clustered installations. |
| [!INCLUDEsssql15-md] Standard** | [!INCLUDEsssql15-md] Enterprise (Server+CAL or Core License) |
| [!INCLUDEsssql15-md] Developer** | [!INCLUDEsssql15-md] Enterprise (Server+CAL or Core License) [!INCLUDEsssql15-md] Web [!INCLUDEsssql15-md] Standard |
| [!INCLUDEsssql15-md] Web | [!INCLUDEsssql15-md] Enterprise (Server+CAL or Core License) [!INCLUDEsssql15-md] Standard |
| [!INCLUDEsssql15-md] Express* | [!INCLUDEsssql15-md] Enterprise (Server+CAL or Core License) [!INCLUDEsssql15-md] Developer [!INCLUDEsssql15-md] Standard [!INCLUDEsssql15-md] Web |
Additionally you can also perform an edition upgrade between [!INCLUDEsssql15-md] Enterprise (Server+CAL license) and [!INCLUDEsssql15-md] Enterprise (Core License):
| Edition Upgrade From | Edition Upgrade To |
|---|---|
| [!INCLUDEsssql15-md] Enterprise (Server+CAL License)** | [!INCLUDEsssql15-md] Enterprise (Core License) |
| [!INCLUDEsssql15-md] Enterprise (Core License) | [!INCLUDEsssql15-md] Enterprise (Server+CAL License) |
* Also applies to [!INCLUDEsssql15-md] Express with Tools and [!INCLUDEsssql15-md] Express with Advanced Services.
** Changing the edition of a [!INCLUDEsssql15-md] failover cluster is limited. The following scenarios are not supported for [!INCLUDEsssql15-md] failover clusters:
-
[!INCLUDEsssql15-md] Enterprise to [!INCLUDEsssql15-md] Developer, Standard, or Evaluation.
-
[!INCLUDEsssql15-md] Developer to [!INCLUDEsssql15-md] Standard or Evaluation.
-
[!INCLUDEsssql15-md] Standard to [!INCLUDEsssql15-md] Evaluation.
-
[!INCLUDEsssql15-md] Evaluation to [!INCLUDEsssql15-md] Standard.
Editions and Supported Features for SQL Server 2016
Hardware and Software Requirements for Installing SQL Server 2016
Upgrade to SQL Server 2016