| title | Supported Version and Edition Upgrades (SQL Server 2017) | ||||
|---|---|---|---|---|---|
| description | The supported version and edition upgrades for SQL Server 2017. | ||||
| author | rwestMSFT | ||||
| ms.author | randolphwest | ||||
| ms.date | 06/03/2025 | ||||
| ms.service | sql | ||||
| ms.subservice | install | ||||
| ms.topic | upgrade-and-migration-article | ||||
| helpviewer_keywords |
|
||||
| monikerRange | >=sql-server-2016 |
[!INCLUDE SQL Server -Windows Only]
You can upgrade from [!INCLUDE sql2008-md], [!INCLUDE sql2008r2], [!INCLUDE ssSQL11], [!INCLUDE ssSQL14], and [!INCLUDE sssql15-md]. This article lists the supported upgrade paths from these [!INCLUDE ssNoVersion] versions, and the supported edition upgrades for [!INCLUDE sssql17-md].
Before upgrading from one edition of [!INCLUDE sssql17-md] to another, verify that the functionality you're currently using is supported in the edition to which you're moving.
Before upgrading [!INCLUDE ssNoVersion], enable Windows Authentication for [!INCLUDE ssNoVersion] Agent and verify the default configuration: that the [!INCLUDE ssNoVersion] Agent service account is a member of the [!INCLUDE ssNoVersion] sysadmin group.
To upgrade to [!INCLUDE sssql17-md], you must be running a supported operating system. For more information, see Hardware and software requirements for SQL Server 2016 and SQL Server 2017.
Upgrade is blocked if there's a pending restart.
Upgrade is blocked if the Windows Installer service isn't running.
-
Cross-version instances of [!INCLUDE sssql17-md] aren't supported. Version numbers of the [!INCLUDE ssDE] components must be the same in an instance of [!INCLUDE sssql17-md].
-
[!INCLUDE sssql17-md] is only available for 64-bit platforms. Cross-platform upgrade isn't supported. You can't upgrade a 32-bit instance of [!INCLUDE ssNoVersion] to native 64-bit using [!INCLUDE ssNoVersion] Setup. However, you can back up or detach databases from a 32-bit instance of [!INCLUDE ssNoVersion], and then restore or attach them to a new instance of [!INCLUDE ssNoVersion] (64-bit) if the databases aren't published in replication. You must re-create any logins and other user objects in
master,msdb, andmodelsystem databases. -
You can't add new features during the upgrade of your existing instance of [!INCLUDE ssNoVersion]. After you upgrade an instance of [!INCLUDE ssNoVersion] to [!INCLUDE sssql17-md], you can add features by using the [!INCLUDE sssql17-md] Setup. For more information, see Add Features to an Instance of SQL Server (Setup).
-
Failover Clusters aren't supported in WOW mode.
[!INCLUDE sssql17-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 [!INCLUDE ssVersion2005] see Support for 2005.
The following table lists the supported upgrade scenarios from earlier versions of [!INCLUDE ssNoVersion] to [!INCLUDE sssql17-md].
| Upgrade from | Supported upgrade path |
|---|---|
| [!INCLUDE sql2008-md] SP4 Enterprise | [!INCLUDE sssql17-md] Enterprise |
| [!INCLUDE sql2008-md] SP4 Developer | [!INCLUDE sssql17-md] Developer |
| [!INCLUDE sql2008-md] SP4 Standard | [!INCLUDE sssql17-md] Enterprise [!INCLUDE sssql17-md] Standard |
| [!INCLUDE sql2008-md] SP4 Small Business | [!INCLUDE sssql17-md] Standard |
| [!INCLUDE sql2008-md] SP4 Web | [!INCLUDE sssql17-md] Enterprise [!INCLUDE sssql17-md] Standard [!INCLUDE sssql17-md] Web |
| [!INCLUDE sql2008-md] SP4 Workgroup | [!INCLUDE sssql17-md] Enterprise [!INCLUDE sssql17-md] Standard |
| [!INCLUDE sql2008-md] SP4 Express | [!INCLUDE sssql17-md] Enterprise [!INCLUDE sssql17-md] Standard [!INCLUDE sssql17-md] Web [!INCLUDE sssql17-md] Express |
| [!INCLUDE sql2008r2] SP3 Datacenter | [!INCLUDE sssql17-md] Enterprise |
| [!INCLUDE sql2008r2] SP3 Enterprise | [!INCLUDE sssql17-md] Enterprise |
| [!INCLUDE sql2008r2] SP3 Developer | [!INCLUDE sssql17-md] Developer |
| [!INCLUDE sql2008r2] SP3 Small Business | [!INCLUDE sssql17-md] Standard |
| [!INCLUDE sql2008r2] SP3 Standard | [!INCLUDE sssql17-md] Enterprise [!INCLUDE sssql17-md] Standard |
| [!INCLUDE sql2008r2] SP3 Web | [!INCLUDE sssql17-md] Enterprise [!INCLUDE sssql17-md] Standard [!INCLUDE sssql17-md] Web |
| [!INCLUDE sql2008r2] SP3 Workgroup | [!INCLUDE sssql17-md] Enterprise [!INCLUDE sssql17-md] Standard |
| [!INCLUDE sql2008r2] SP3 Express | [!INCLUDE sssql17-md] Enterprise [!INCLUDE sssql17-md] Standard [!INCLUDE sssql17-md] Web [!INCLUDE sssql17-md] Express |
| [!INCLUDE ssSQL11] SP2 Enterprise | [!INCLUDE sssql17-md] Enterprise |
| [!INCLUDE ssSQL11] SP2 Developer | [!INCLUDE sssql17-md] Developer [!INCLUDE sssql17-md] Standard [!INCLUDE sssql17-md] Web [!INCLUDE sssql17-md] Enterprise |
| [!INCLUDE ssSQL11] SP2 Standard | [!INCLUDE sssql17-md] Enterprise [!INCLUDE sssql17-md] Standard |
| [!INCLUDE ssSQL11] SP1 Web | [!INCLUDE sssql17-md] Enterprise [!INCLUDE sssql17-md] Standard [!INCLUDE sssql17-md] Web |
| [!INCLUDE ssSQL11] SP2 Express | [!INCLUDE sssql17-md] Enterprise [!INCLUDE sssql17-md] Standard [!INCLUDE sssql17-md] Web [!INCLUDE sssql17-md] Express |
| [!INCLUDE ssSQL11] SP2 Business Intelligence | [!INCLUDE sssql17-md] Enterprise |
| [!INCLUDE ssSQL11] SP2 Evaluation | [!INCLUDE sssql17-md] Evaluation [!INCLUDE sssql17-md] Enterprise [!INCLUDE sssql17-md] Standard [!INCLUDE sssql17-md] Web [!INCLUDE sssql17-md] Developer |
| [!INCLUDE ssSQL14] Enterprise | [!INCLUDE sssql17-md] Enterprise |
| [!INCLUDE ssSQL14] Developer | [!INCLUDE sssql17-md] Developer [!INCLUDE sssql17-md] Standard [!INCLUDE sssql17-md] Web [!INCLUDE sssql17-md] Enterprise |
| [!INCLUDE ssSQL14] Standard | [!INCLUDE sssql17-md] Enterprise [!INCLUDE sssql17-md] Standard |
| [!INCLUDE ssSQL14] Web | [!INCLUDE sssql17-md] Enterprise [!INCLUDE sssql17-md] Standard [!INCLUDE sssql17-md] Web |
| [!INCLUDE ssSQL14] Express | [!INCLUDE sssql17-md] Enterprise [!INCLUDE sssql17-md] Standard [!INCLUDE sssql17-md] Web [!INCLUDE sssql17-md] Express [!INCLUDE sssql17-md] Developer |
| [!INCLUDE ssSQL14] Business Intelligence | [!INCLUDE sssql17-md] Enterprise |
| [!INCLUDE ssSQL14] Evaluation | [!INCLUDE sssql17-md] Evaluation [!INCLUDE sssql17-md] Enterprise [!INCLUDE sssql17-md] Standard [!INCLUDE sssql17-md] Web [!INCLUDE sssql17-md] Developer |
| [!INCLUDE sssql16-md] Enterprise | [!INCLUDE sssql17-md] Enterprise |
| [!INCLUDE sssql16-md] Developer | [!INCLUDE sssql17-md] Developer [!INCLUDE sssql17-md] Standard [!INCLUDE sssql17-md] Web [!INCLUDE sssql17-md] Enterprise |
| [!INCLUDE sssql16-md] Standard | [!INCLUDE sssql17-md] Enterprise [!INCLUDE sssql17-md] Standard |
| [!INCLUDE sssql16-md] Web | [!INCLUDE sssql17-md] Enterprise [!INCLUDE sssql17-md] Standard [!INCLUDE sssql17-md] Web |
| [!INCLUDE sssql16-md] Express | [!INCLUDE sssql17-md] Enterprise [!INCLUDE sssql17-md] Standard [!INCLUDE sssql17-md] Web [!INCLUDE sssql17-md] Express [!INCLUDE sssql17-md] Developer |
| [!INCLUDE sssql16-md] Business Intelligence | [!INCLUDE sssql17-md] Enterprise |
| [!INCLUDE sssql16-md] Evaluation | [!INCLUDE sssql17-md] Evaluation [!INCLUDE sssql17-md] Enterprise [!INCLUDE sssql17-md] Standard [!INCLUDE sssql17-md] Web [!INCLUDE sssql17-md] Developer |
| [!INCLUDE sssql17-md] release candidate 1 | [!INCLUDE sssql17-md] Enterprise |
| [!INCLUDE sssql17-md] Developer | [!INCLUDE sssql17-md] Enterprise |
1 Microsoft support to upgrade from release candidate software is specifically for customers who participated in the Technology Adoption Program (TAP).
This section discusses [!INCLUDE sssql17-md] support for [!INCLUDE ssVersion2005]. In [!INCLUDE sssql17-md], you can:
-
Attach a [!INCLUDE ssVersion2005] database (mdf/ldf files) to [!INCLUDE sssql17-md] instance of database engine.
-
Restore a [!INCLUDE ssVersion2005] database to [!INCLUDE sssql17-md] instance of database engine from a backup.
-
Back up a [!INCLUDE ssASversion2005] cube and restore it on [!INCLUDE sssql17-md].
When a [!INCLUDE ssVersion2005] database is upgraded to [!INCLUDE sssql17-md], the database compatibility level is changed from 90 to 100. (In [!INCLUDE sssql17-md], valid values for the database compatibility level are 100, 110, 120, 130, and 140.) ALTER DATABASE (Transact-SQL) compatibility level discusses how the compatibility level change could affect [!INCLUDE ssNoVersion] applications.
Any scenarios not specified in the previous list aren't supported, including but not limited to:
-
Installing [!INCLUDE ssVersion2005] and [!INCLUDE sssql17-md] on same computer (side by side).
-
Using a [!INCLUDE ssVersion2005] instance as a member of the replication topology that involves a [!INCLUDE sssql17-md] instance.
-
Configuring database mirroring between [!INCLUDE sssql17-md] and [!INCLUDE ssVersion2005] instances.
-
Backing up the transaction log with log shipping between [!INCLUDE sssql17-md] and [!INCLUDE ssVersion2005] instances.
-
Configuring linked servers between [!INCLUDE sssql17-md] and [!INCLUDE ssVersion2005] instances.
-
Managing a [!INCLUDE ssVersion2005] instance from a [!INCLUDE sssql17-md] Management Studio.
-
Attaching a [!INCLUDE ssASversion2005] cube in [!INCLUDE sssql17-md] Management Studio.
-
Connecting to [!INCLUDE ssISversion2005] from [!INCLUDE sssql17-md] Management Studio.
-
Managing a [!INCLUDE ssISversion2005] service from [!INCLUDE sssql17-md] Management Studio.
-
Support for [!INCLUDE ssVersion2005] third party custom Integration Services components, such as execute and upgrade.
The following table lists the supported edition upgrade scenarios in [!INCLUDE sssql17-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 |
|---|---|
| [!INCLUDE sssql17-md] Enterprise (Server+CAL and Core) 2 | [!INCLUDE sssql17-md] Enterprise |
| [!INCLUDE sssql17-md] Evaluation Enterprise 2 | [!INCLUDE sssql17-md] Enterprise (Server+CAL or Core License) [!INCLUDE sssql17-md] Standard [!INCLUDE sssql17-md] Developer [!INCLUDE sssql17-md] Web Upgrading from Evaluation (a free edition) to any of the paid editions is supported for stand-alone installations, but isn't supported for clustered installations. This limitation doesn't apply to stand-alone instances installed on a Windows Failover Cluster participating in an availability group. |
| [!INCLUDE sssql17-md] Standard 2 | [!INCLUDE sssql17-md] Enterprise (Server+CAL or Core License) |
| [!INCLUDE sssql17-md] Developer 2 | [!INCLUDE sssql17-md] Enterprise (Server+CAL or Core License) [!INCLUDE sssql17-md] Web [!INCLUDE sssql17-md] Standard |
| [!INCLUDE sssql17-md] Web | [!INCLUDE sssql17-md] Enterprise (Server+CAL or Core License) [!INCLUDE sssql17-md] Standard |
| [!INCLUDE sssql17-md] Express 1 | [!INCLUDE sssql17-md] Enterprise (Server+CAL or Core License) [!INCLUDE sssql17-md] Developer [!INCLUDE sssql17-md] Standard [!INCLUDE sssql17-md] Web |
1 Also applies to [!INCLUDE sssql17-md] Express with Tools and [!INCLUDE sssql17-md] Express with Advanced Services.
2 Changing the edition of a [!INCLUDE sssql17-md] failover cluster is limited. The following scenarios aren't supported for [!INCLUDE sssql17-md] failover clusters:
Additionally you can also perform an edition upgrade between [!INCLUDE sssql17-md] Enterprise (Server+CAL license) and [!INCLUDE sssql17-md] Enterprise (Core License):
| Edition upgrade from | Edition upgrade to |
|---|---|
| [!INCLUDE sssql17-md] Enterprise (Server+CAL License) 1 | [!INCLUDE sssql17-md] Enterprise (Core License) |
| [!INCLUDE sssql17-md] Enterprise (Core License) | [!INCLUDE sssql17-md] Enterprise (Server+CAL License) |
1 Changing the edition of a [!INCLUDE sssql17-md] failover cluster is limited. The following scenarios aren't supported for [!INCLUDE sssql17-md] failover clusters:
- [!INCLUDE sssql17-md] Enterprise to [!INCLUDE sssql17-md] Developer, Standard, or Evaluation.
- [!INCLUDE sssql17-md] Developer to [!INCLUDE sssql17-md] Standard or Evaluation.
- [!INCLUDE sssql17-md] Standard to [!INCLUDE sssql17-md] Evaluation.
- [!INCLUDE sssql17-md] Evaluation to [!INCLUDE sssql17-md] Standard.