| title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | helpviewer_keywords | monikerRange | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Supported version and edition upgrades (SQL Server 2017) |
The supported version and edition upgrades for SQL Server 2017. |
rwestMSFT |
randolphwest |
12/13/2019 |
sql |
install |
upgrade-and-migration-article |
|
>=sql-server-2016 |
[!INCLUDE SQL Server -Windows Only]
You can upgrade from [!INCLUDEsql2008-md], [!INCLUDEsql2008r2], [!INCLUDEssSQL11], [!INCLUDEssSQL14], and [!INCLUDEsssql15-md]. This article lists the supported upgrade paths from these [!INCLUDEssNoVersion] versions, and the supported edition upgrades for [!INCLUDEsssql17-md].
-
Before upgrading from one edition of [!INCLUDEsssql17-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 [!INCLUDEsssql17-md], you must be running a supported operating system. For more information, see Hardware and Software Requirements for Installing SQL Server.
-
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 [!INCLUDEsssql17-md] are not supported. Version numbers of the [!INCLUDEssDE] components must be the same in an instance of [!INCLUDEsssql17-md].
-
[!INCLUDEsssql17-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 [!INCLUDEsssql17-md], you can add features by using the [!INCLUDEsssql17-md] Setup. For more information, see Add Features to an Instance of SQL Server (Setup).
-
Failover Clusters are not supported in WOW mode.
Upgrades from Earlier Versions to [!INCLUDEsssql17-md]
[!INCLUDEsssql17-md] supports upgrade from the following versions of SQL Server:
- SQL Server 2008 SP4 or later
- SQL Server 2008 R2 SP3 or later
- SQL Server 2012 SP2 or later
- SQL Server 2014 or later
- SQL Server 2016 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 [!INCLUDEsssql17-md].
| Upgrade from | Supported upgrade path |
|---|---|
| [!INCLUDEsql2008-md] SP4 Enterprise | [!INCLUDEsssql17-md] Enterprise |
| [!INCLUDEsql2008-md] SP4 Developer | [!INCLUDEsssql17-md] Developer |
| [!INCLUDEsql2008-md] SP4 Standard | [!INCLUDEsssql17-md] Enterprise [!INCLUDEsssql17-md] Standard |
| [!INCLUDEsql2008-md] SP4 Small Business | [!INCLUDEsssql17-md] Standard |
| [!INCLUDEsql2008-md] SP4 Web | [!INCLUDEsssql17-md] Enterprise [!INCLUDEsssql17-md] Standard [!INCLUDEsssql17-md] Web |
| [!INCLUDEsql2008-md] SP4 Workgroup | [!INCLUDEsssql17-md] Enterprise [!INCLUDEsssql17-md] Standard |
| [!INCLUDEsql2008-md] SP4 Express | [!INCLUDEsssql17-md] Enterprise [!INCLUDEsssql17-md] Standard [!INCLUDEsssql17-md] Web [!INCLUDEsssql17-md] Express |
| [!INCLUDEsql2008r2] SP3 Datacenter | [!INCLUDEsssql17-md] Enterprise |
| [!INCLUDEsql2008r2] SP3 Enterprise | [!INCLUDEsssql17-md] Enterprise |
| [!INCLUDEsql2008r2] SP3 Developer | [!INCLUDEsssql17-md] Developer |
| [!INCLUDEsql2008r2] SP3 Small Business | [!INCLUDEsssql17-md] Standard |
| [!INCLUDEsql2008r2] SP3 Standard | [!INCLUDEsssql17-md] Enterprise [!INCLUDEsssql17-md] Standard |
| [!INCLUDEsql2008r2] SP3 Web | [!INCLUDEsssql17-md] Enterprise [!INCLUDEsssql17-md] Standard [!INCLUDEsssql17-md] Web |
| [!INCLUDEsql2008r2] SP3 Workgroup | [!INCLUDEsssql17-md] Enterprise [!INCLUDEsssql17-md] Standard |
| [!INCLUDEsql2008r2] SP3 Express | [!INCLUDEsssql17-md] Enterprise [!INCLUDEsssql17-md] Standard [!INCLUDEsssql17-md] Web [!INCLUDEsssql17-md] Express |
| [!INCLUDEssSQL11] SP2 Enterprise | [!INCLUDEsssql17-md] Enterprise |
| [!INCLUDEssSQL11] SP2 Developer | [!INCLUDEsssql17-md] Developer [!INCLUDEsssql17-md] Standard [!INCLUDEsssql17-md] Web [!INCLUDEsssql17-md] Enterprise |
| [!INCLUDEssSQL11] SP2 Standard | [!INCLUDEsssql17-md] Enterprise [!INCLUDEsssql17-md] Standard |
| [!INCLUDEssSQL11] SP1 Web | [!INCLUDEsssql17-md] Enterprise [!INCLUDEsssql17-md] Standard [!INCLUDEsssql17-md] Web |
| [!INCLUDEssSQL11] SP2 Express | [!INCLUDEsssql17-md] Enterprise [!INCLUDEsssql17-md] Standard [!INCLUDEsssql17-md] Web [!INCLUDEsssql17-md] Express |
| [!INCLUDEssSQL11] SP2 Business Intelligence | [!INCLUDEsssql17-md] Enterprise |
| [!INCLUDEssSQL11] SP2 Evaluation | [!INCLUDEsssql17-md] Evaluation [!INCLUDEsssql17-md] Enterprise [!INCLUDEsssql17-md] Standard [!INCLUDEsssql17-md] Web [!INCLUDEsssql17-md] Developer |
| [!INCLUDEssSQL14] Enterprise | [!INCLUDEsssql17-md] Enterprise |
| [!INCLUDEssSQL14] Developer | [!INCLUDEsssql17-md] Developer [!INCLUDEsssql17-md] Standard [!INCLUDEsssql17-md] Web [!INCLUDEsssql17-md] Enterprise |
| [!INCLUDEssSQL14] Standard | [!INCLUDEsssql17-md] Enterprise [!INCLUDEsssql17-md] Standard |
| [!INCLUDEssSQL14] Web | [!INCLUDEsssql17-md] Enterprise [!INCLUDEsssql17-md] Standard [!INCLUDEsssql17-md] Web |
| [!INCLUDEssSQL14] Express | [!INCLUDEsssql17-md] Enterprise [!INCLUDEsssql17-md] Standard [!INCLUDEsssql17-md] Web [!INCLUDEsssql17-md] Express [!INCLUDEsssql17-md] Developer |
| [!INCLUDEssSQL14] Business Intelligence | [!INCLUDEsssql17-md] Enterprise |
| [!INCLUDEssSQL14] Evaluation | [!INCLUDEsssql17-md] Evaluation [!INCLUDEsssql17-md] Enterprise [!INCLUDEsssql17-md] Standard [!INCLUDEsssql17-md] Web [!INCLUDEsssql17-md] Developer |
| [!INCLUDEsssql16-md] Enterprise | [!INCLUDEsssql17-md] Enterprise |
| [!INCLUDEsssql16-md] Developer | [!INCLUDEsssql17-md] Developer [!INCLUDEsssql17-md] Standard [!INCLUDEsssql17-md] Web [!INCLUDEsssql17-md] Enterprise |
| [!INCLUDEsssql16-md] Standard | [!INCLUDEsssql17-md] Enterprise [!INCLUDEsssql17-md] Standard |
| [!INCLUDEsssql16-md] Web | [!INCLUDEsssql17-md] Enterprise [!INCLUDEsssql17-md] Standard [!INCLUDEsssql17-md] Web |
| [!INCLUDEsssql16-md] Express | [!INCLUDEsssql17-md] Enterprise [!INCLUDEsssql17-md] Standard [!INCLUDEsssql17-md] Web [!INCLUDEsssql17-md] Express [!INCLUDEsssql17-md] Developer |
| [!INCLUDEsssql16-md] Business Intelligence | [!INCLUDEsssql17-md] Enterprise |
| [!INCLUDEsssql16-md] Evaluation | [!INCLUDEsssql17-md] Evaluation [!INCLUDEsssql17-md] Enterprise [!INCLUDEsssql17-md] Standard [!INCLUDEsssql17-md] Web [!INCLUDEsssql17-md] Developer |
| [!INCLUDEsssql17-md] release candidate* | [!INCLUDEsssql17-md] Enterprise |
| [!INCLUDE sssql17-md] Developer | [!INCLUDEsssql17-md] Enterprise |
* Microsoft support to upgrade from release candidate software is specifically for customers who participated in the Technology Adoption Program (TAP).
[!INCLUDEsssql17-md] Support for [!INCLUDEssVersion2005]
This section discusses [!INCLUDEsssql17-md] support for [!INCLUDEssVersion2005]. In [!INCLUDEsssql17-md], you will be able to do the following:
-
Attach a [!INCLUDEssVersion2005] database (mdf/ldf files) to [!INCLUDEsssql17-md] instance of database engine.
-
Restore a [!INCLUDEssVersion2005] database to [!INCLUDEsssql17-md] instance of database engine from a backup.
-
Back up a [!INCLUDEssASversion2005] cube and restore it on [!INCLUDEsssql17-md].
When a [!INCLUDEssVersion2005] database is upgraded to [!INCLUDEsssql17-md], the database compatibility level will be changed from 90 to 100. (In [!INCLUDEsssql17-md], valid values for the database compatibility level are 100, 110, 120, 130, and 140.) 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 [!INCLUDEsssql17-md] on same computer (side by side).
-
Using a [!INCLUDEssVersion2005] instance as a member of the replication topology that involves a [!INCLUDEsssql17-md] instance.
-
Configuring database mirroring between [!INCLUDEsssql17-md] and [!INCLUDEssVersion2005] instances.
-
Backing up the transaction log with log shipping between [!INCLUDEsssql17-md] and [!INCLUDEssVersion2005] instances.
-
Configuring linked servers between [!INCLUDEsssql17-md] and [!INCLUDEssVersion2005] instances.
-
Managing a [!INCLUDEssVersion2005] instance from a [!INCLUDEsssql17-md] Management Studio.
-
Attaching a [!INCLUDEssASversion2005] cube in [!INCLUDEsssql17-md] Management Studio.
-
Connecting to [!INCLUDEssISversion2005] from [!INCLUDEsssql17-md] Management Studio.
-
Managing a [!INCLUDEssISversion2005] service from [!INCLUDEsssql17-md] Management Studio.
-
Support for [!INCLUDEssVersion2005] third party custom Integration Services components, such as execute and upgrade.
[!INCLUDEsssql17-md] Edition Upgrade
The following table lists the supported edition upgrade scenarios in [!INCLUDEsssql17-md].
For step-by-step instructions on how to perform an edition upgrade, see Upgrade to a Different Edition of SQL Server (Setup).
| Upgrade From | Upgrade To |
|---|---|
| [!INCLUDEsssql17-md] Enterprise (Server+CAL and Core)** | [!INCLUDEsssql17-md] Enterprise |
| [!INCLUDEsssql17-md] Evaluation Enterprise** | [!INCLUDEsssql17-md] Enterprise (Server+CAL or Core License) [!INCLUDEsssql17-md] Standard [!INCLUDEsssql17-md] Developer [!INCLUDEsssql17-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. This limitation does not apply to stand-alone instances installed on a Windows Failover Cluster participating in an availability group. |
| [!INCLUDEsssql17-md] Standard** | [!INCLUDEsssql17-md] Enterprise (Server+CAL or Core License) |
| [!INCLUDEsssql17-md] Developer** | [!INCLUDEsssql17-md] Enterprise (Server+CAL or Core License) [!INCLUDEsssql17-md] Web [!INCLUDEsssql17-md] Standard |
| [!INCLUDEsssql17-md] Web | [!INCLUDEsssql17-md] Enterprise (Server+CAL or Core License) [!INCLUDEsssql17-md] Standard |
| [!INCLUDEsssql17-md] Express* | [!INCLUDEsssql17-md] Enterprise (Server+CAL or Core License) [!INCLUDEsssql17-md] Developer [!INCLUDEsssql17-md] Standard [!INCLUDEsssql17-md] Web |
Additionally you can also perform an edition upgrade between [!INCLUDEsssql17-md] Enterprise (Server+CAL license) and [!INCLUDEsssql17-md] Enterprise (Core License):
| Edition Upgrade From | Edition Upgrade To |
|---|---|
| [!INCLUDEsssql17-md] Enterprise (Server+CAL License)** | [!INCLUDEsssql17-md] Enterprise (Core License) |
| [!INCLUDEsssql17-md] Enterprise (Core License) | [!INCLUDEsssql17-md] Enterprise (Server+CAL License) |
* Also applies to [!INCLUDEsssql17-md] Express with Tools and [!INCLUDEsssql17-md] Express with Advanced Services.
** Changing the edition of a [!INCLUDEsssql17-md] failover cluster is limited. The following scenarios are not supported for [!INCLUDEsssql17-md] failover clusters:
-
[!INCLUDEsssql17-md] Enterprise to [!INCLUDEsssql17-md] Developer, Standard, or Evaluation.
-
[!INCLUDEsssql17-md] Developer to [!INCLUDEsssql17-md] Standard or Evaluation.
-
[!INCLUDEsssql17-md] Standard to [!INCLUDEsssql17-md] Evaluation.
-
[!INCLUDEsssql17-md] Evaluation to [!INCLUDEsssql17-md] Standard.