Skip to content

Latest commit

 

History

History
174 lines (121 loc) · 19.6 KB

supported-version-and-edition-upgrades.md

File metadata and controls

174 lines (121 loc) · 19.6 KB
title description author ms.author ms.reviewer ms.date ms.service ms.subservice ms.topic helpviewer_keywords monikerRange
Supported Version and Edition Upgrades (SQL Server 2016)
The supported version and edition upgrades for SQL Server 2016.
rwestMSFT
randolphwest
vanto
09/17/2024
sql
install
upgrade-and-migration-article
components [SQL Server], adding to existing installations
versions [SQL Server], upgrading
upgrading SQL Server, upgrades supported
cross-language support
>=sql-server-2016

Supported version & edition upgrades (SQL Server 2016)

[!INCLUDE SQL Server -Windows Only]

You can upgrade from [!INCLUDE sql2008-md], [!INCLUDE sql2008r2], [!INCLUDE ssSQL11], and [!INCLUDE ssSQL14]. This article lists the supported upgrade paths from these [!INCLUDE ssNoVersion] versions, and the supported edition upgrades for [!INCLUDE sssql15-md].

Pre upgrade Checklist

  • Before upgrading from one edition of [!INCLUDE sssql15-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 sssql15-md], you must be running a supported operating system. For more information, see SQL Server 2016 and 2017: Hardware and software requirements.

  • Upgrade is blocked if there's a pending restart.

  • Upgrade is blocked if the Windows Installer service isn't running.

Unsupported Scenarios

  • Cross-version instances of [!INCLUDE sssql15-md] aren't supported. Version numbers of the [!INCLUDE ssDE], [!INCLUDE ssASnoversion], and [!INCLUDE ssRSnoversion] components must be the same in an instance of [!INCLUDE sssql15-md].

  • [!INCLUDE sssql15-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, and model system 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 sssql15-md], you can add features by using the [!INCLUDE sssql15-md] Setup. For more information, see Add Features to an Instance of SQL Server (Setup).

  • Failover Clusters aren't supported in WOW mode.

  • Upgrade from an Evaluation edition of a previous [!INCLUDE ssNoVersion] version isn't 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 [!INCLUDE sssql15-md]

SQL Server 2016 supports upgrade from the following versions of SQL Server:

Note

To upgrade databases on [!INCLUDE ssVersion2005] see Support for 2005.

The table below lists the supported upgrade scenarios from earlier versions of [!INCLUDE ssNoVersion] to [!INCLUDE sssql15-md].

Upgrade from Supported upgrade path
[!INCLUDE sql2008-md] SP4 Enterprise [!INCLUDE sssql15-md] Enterprise
[!INCLUDE sql2008-md] SP4 Developer [!INCLUDE sssql15-md] Developer
[!INCLUDE sql2008-md] SP4 Standard [!INCLUDE sssql15-md] Enterprise

[!INCLUDE sssql15-md] Standard
[!INCLUDE sql2008-md] SP4 Small Business [!INCLUDE sssql15-md] Standard
[!INCLUDE sql2008-md] SP4 Web [!INCLUDE sssql15-md] Enterprise

[!INCLUDE sssql15-md] Standard
[!INCLUDE sssql15-md] Web
[!INCLUDE sql2008-md] SP4 Workgroup [!INCLUDE sssql15-md] Enterprise

[!INCLUDE sssql15-md] Standard
[!INCLUDE sql2008-md] SP4 Express [!INCLUDE sssql15-md] Enterprise

[!INCLUDE sssql15-md] Standard
[!INCLUDE sssql15-md] Web
[!INCLUDE sssql15-md] Express
[!INCLUDE sql2008r2] SP3 Datacenter [!INCLUDE sssql15-md] Enterprise
[!INCLUDE sql2008r2] SP3 Enterprise [!INCLUDE sssql15-md] Enterprise
[!INCLUDE sql2008r2] SP3 Developer [!INCLUDE sssql15-md] Developer
[!INCLUDE sql2008r2] SP3 Small Business [!INCLUDE sssql15-md] Standard
[!INCLUDE sql2008r2] SP3 Standard [!INCLUDE sssql15-md] Enterprise

[!INCLUDE sssql15-md] Standard
[!INCLUDE sql2008r2] SP3 Web [!INCLUDE sssql15-md] Enterprise

[!INCLUDE sssql15-md] Standard
[!INCLUDE sssql15-md] Web
[!INCLUDE sql2008r2] SP3 Workgroup [!INCLUDE sssql15-md] Enterprise

[!INCLUDE sssql15-md] Standard
[!INCLUDE sql2008r2] SP3 Express [!INCLUDE sssql15-md] Enterprise

[!INCLUDE sssql15-md] Standard
[!INCLUDE sssql15-md] Web
[!INCLUDE sssql15-md] Express
[!INCLUDE ssSQL11] SP2 Enterprise [!INCLUDE sssql15-md] Enterprise
[!INCLUDE ssSQL11] SP2 Developer [!INCLUDE sssql15-md] Developer

[!INCLUDE sssql15-md] Standard
[!INCLUDE sssql15-md] Web
[!INCLUDE sssql15-md] Enterprise
[!INCLUDE ssSQL11] SP2 Standard [!INCLUDE sssql15-md] Enterprise

[!INCLUDE sssql15-md] Standard
[!INCLUDE ssSQL11] SP1 Web [!INCLUDE sssql15-md] Enterprise

[!INCLUDE sssql15-md] Standard
[!INCLUDE sssql15-md] Web
[!INCLUDE ssSQL11] SP2 Express [!INCLUDE sssql15-md] Enterprise

[!INCLUDE sssql15-md] Standard
[!INCLUDE sssql15-md] Web
[!INCLUDE sssql15-md] Express
[!INCLUDE ssSQL11] SP2 Business Intelligence [!INCLUDE sssql15-md] Enterprise
[!INCLUDE ssSQL11] SP2 Evaluation [!INCLUDE sssql15-md] Evaluation

[!INCLUDE sssql15-md] Enterprise
[!INCLUDE sssql15-md] Standard
[!INCLUDE sssql15-md] Web
[!INCLUDE sssql15-md] Developer
[!INCLUDE ssSQL14] Enterprise [!INCLUDE sssql15-md] Enterprise
[!INCLUDE ssSQL14] Developer [!INCLUDE sssql15-md] Developer

[!INCLUDE sssql15-md] Standard
[!INCLUDE sssql15-md] Web
[!INCLUDE sssql15-md] Enterprise
[!INCLUDE ssSQL14] Standard [!INCLUDE sssql15-md] Enterprise

[!INCLUDE sssql15-md] Standard
[!INCLUDE ssSQL14] Web [!INCLUDE sssql15-md] Enterprise

[!INCLUDE sssql15-md] Standard
[!INCLUDE sssql15-md] Web
[!INCLUDE ssSQL14] Express [!INCLUDE sssql15-md] Enterprise

[!INCLUDE sssql15-md] Standard
[!INCLUDE sssql15-md] Web
[!INCLUDE sssql15-md] Express
[!INCLUDE sssql15-md] Developer
[!INCLUDE ssSQL14] Business Intelligence [!INCLUDE sssql15-md] Enterprise
[!INCLUDE ssSQL14] Evaluation [!INCLUDE sssql15-md] Evaluation

[!INCLUDE sssql15-md] Enterprise
[!INCLUDE sssql15-md] Standard
[!INCLUDE sssql15-md] Web
[!INCLUDE sssql15-md] Developer
[!INCLUDE ssSQL15_md] release candidate* [!INCLUDE sssql15-md] Enterprise
[!INCLUDE ssSQL15_md] Developer [!INCLUDE sssql15-md] Enterprise

* Microsoft support to upgrade from release candidate software is specifically for customers who participated in the Technology Adoption Program (TAP).

[!INCLUDE sssql15-md] Support for [!INCLUDE ssVersion2005]

This section discusses [!INCLUDE sssql15-md] support for [!INCLUDE ssVersion2005]. In [!INCLUDE sssql15-md], you'll be able to do the following:

Note

When a [!INCLUDE ssVersion2005] database is upgraded to [!INCLUDE sssql15-md], the database compatibility level will be changed from 90 to 100.
In [!INCLUDE sssql15-md], valid values for the database compatibility level are 100, 110, 120, and 130. ALTER DATABASE (Transact-SQL) compatibility level discusses how the compatibility level change could affect [!INCLUDE ssNoVersion] applications.

Any scenarios not specified in the list above aren't supported, including but not limited to the following:

[!INCLUDE sssql15-md] Edition Upgrade

The following table lists the supported edition upgrade scenarios in [!INCLUDE sssql15-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 sssql15-md] Enterprise (Server+CAL and Core)** [!INCLUDE sssql15-md] Enterprise
[!INCLUDE sssql15-md] Evaluation Enterprise** [!INCLUDE sssql15-md] Enterprise (Server+CAL or Core License)

[!INCLUDE sssql15-md] Standard
[!INCLUDE sssql15-md] Developer
[!INCLUDE sssql15-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 sssql15-md] Standard** [!INCLUDE sssql15-md] Enterprise (Server+CAL or Core License)
[!INCLUDE sssql15-md] Developer** [!INCLUDE sssql15-md] Enterprise (Server+CAL or Core License)

[!INCLUDE sssql15-md] Web
[!INCLUDE sssql15-md] Standard
[!INCLUDE sssql15-md] Web [!INCLUDE sssql15-md] Enterprise (Server+CAL or Core License)

[!INCLUDE sssql15-md] Standard
[!INCLUDE sssql15-md] Express* [!INCLUDE sssql15-md] Enterprise (Server+CAL or Core License)

[!INCLUDE sssql15-md] Developer
[!INCLUDE sssql15-md] Standard
[!INCLUDE sssql15-md] Web

Additionally you can also perform an edition upgrade between [!INCLUDE sssql15-md] Enterprise (Server+CAL license) and [!INCLUDE sssql15-md] Enterprise (Core License):

Edition Upgrade From Edition Upgrade To
[!INCLUDE sssql15-md] Enterprise (Server+CAL License)** [!INCLUDE sssql15-md] Enterprise (Core License)
[!INCLUDE sssql15-md] Enterprise (Core License) [!INCLUDE sssql15-md] Enterprise (Server+CAL License)

* Also applies to [!INCLUDE sssql15-md] Express with Tools and [!INCLUDE sssql15-md] Express with Advanced Services.

** Changing the edition of a [!INCLUDE sssql15-md] failover cluster is limited. The following scenarios aren't supported for [!INCLUDE sssql15-md] failover clusters:

Related content