supported-version-and-edition-upgrades-2019.md

title	Supported version and edition upgrades (SQL Server 2019)
description	The supported version and edition upgrades for SQL Server 2019.
author	rwestMSFT
ms.author	randolphwest
ms.date	10/20/2022
ms.prod	sql
ms.technology	install
ms.topic	conceptual
helpviewer_keywords	components [SQL Server], adding to existing installations versions [SQL Server], upgrading upgrading SQL Server, upgrades supported cross-language support
monikerRange	>=sql-server-2017

Supported version and edition upgrades (SQL Server 2019)

[!INCLUDE SQL Server -Windows Only]

You can upgrade from [!INCLUDEssSQL11], [!INCLUDEssSQL14], [!INCLUDEsssql16-md], and [!INCLUDEsssql17-md]. This article lists the supported upgrade paths from these [!INCLUDEssNoVersion] versions, and the supported edition upgrades for [!INCLUDEsssql19-md].

Pre-upgrade checklist

• Before upgrading from one edition of [!INCLUDEsssql19-md] to another, verify that the functionality you're currently using is supported in the edition to which you're moving.
• Verify supported hardware and software.
• 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 [!INCLUDEsssql19-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's a pending restart.
• Upgrade will be blocked if the Windows Installer service isn't running.

Unsupported scenarios

• Cross-version instances of [!INCLUDEsssql19-md] aren't supported. Version numbers of the [!INCLUDEssDE] components must be the same in an instance of [!INCLUDEsssql19-md].

• [!INCLUDEsssql19-md] is only available for 64-bit platforms. Cross-platform upgrade isn't supported. You can't 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 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 [!INCLUDEssNoVersion]. After you upgrade an instance of [!INCLUDEssNoVersion] to [!INCLUDEsssql19-md], you can add features by using the [!INCLUDEsssql19-md] Setup. For more information, see Add Features to an Instance of SQL Server (Setup).

Upgrades from earlier versions to [!INCLUDEsssql19-md]

[!INCLUDEsssql19-md] supports upgrade from the following versions of [!INCLUDEssNoVersion]:

• [!INCLUDEssSQL11] SP4 or later
• [!INCLUDEssSQL14] SP2 or later
• [!INCLUDEssSQL16] RTM or later
• [!INCLUDEsssql17-md]

The following table lists the supported upgrade scenarios from earlier versions of [!INCLUDEssNoVersion] to [!INCLUDEsssql19-md].

Upgrade from	Supported upgrade path
[!INCLUDEssSQL11] SP4 Enterprise	[!INCLUDEsssql19-md] Enterprise
[!INCLUDEssSQL11] SP4 Developer	[!INCLUDEsssql19-md] Developer [!INCLUDEsssql19-md] Standard [!INCLUDEsssql19-md] Web [!INCLUDEsssql19-md] Enterprise
[!INCLUDEssSQL11] SP4 Standard	[!INCLUDEsssql19-md] Enterprise [!INCLUDEsssql19-md] Standard
[!INCLUDEssSQL11] SP4 Web	[!INCLUDEsssql19-md] Enterprise [!INCLUDEsssql19-md] Standard [!INCLUDEsssql19-md] Web
[!INCLUDEssSQL11] SP4 Express	[!INCLUDEsssql19-md] Enterprise [!INCLUDEsssql19-md] Standard [!INCLUDEsssql19-md] Web [!INCLUDEsssql19-md] Express
[!INCLUDEssSQL11] SP4 Business Intelligence	[!INCLUDEsssql19-md] Enterprise
[!INCLUDEssSQL11] SP4 Evaluation	[!INCLUDEsssql19-md] Evaluation [!INCLUDEsssql19-md] Enterprise [!INCLUDEsssql19-md] Standard [!INCLUDEsssql19-md] Web [!INCLUDEsssql19-md] Developer
[!INCLUDEssSQL14] SP2 Enterprise	[!INCLUDEsssql19-md] Enterprise
[!INCLUDEssSQL14] SP2 Developer	[!INCLUDEsssql19-md] Developer [!INCLUDEsssql19-md] Standard [!INCLUDEsssql19-md] Web [!INCLUDEsssql19-md] Enterprise
[!INCLUDEssSQL14] SP2 Standard	[!INCLUDEsssql19-md] Enterprise [!INCLUDEsssql19-md] Standard
[!INCLUDEssSQL14] SP2 Web	[!INCLUDEsssql19-md] Enterprise [!INCLUDEsssql19-md] Standard [!INCLUDEsssql19-md] Web
[!INCLUDEssSQL14] SP2 Express	[!INCLUDEsssql19-md] Enterprise [!INCLUDEsssql19-md] Standard [!INCLUDEsssql19-md] Web [!INCLUDEsssql19-md] Express [!INCLUDEsssql19-md] Developer
[!INCLUDEssSQL14] SP2 Business Intelligence	[!INCLUDEsssql19-md] Enterprise
[!INCLUDEssSQL14] SP2 Evaluation	[!INCLUDEsssql19-md] Evaluation [!INCLUDEsssql19-md] Enterprise [!INCLUDEsssql19-md] Standard [!INCLUDEsssql19-md] Web [!INCLUDEsssql19-md] Developer
[!INCLUDEssSQL16] 13.0.1601.5 Enterprise	[!INCLUDEsssql19-md] Enterprise
[!INCLUDEssSQL16] 13.0.1601.5 Developer	[!INCLUDEsssql19-md] Developer [!INCLUDEsssql19-md] Standard [!INCLUDEsssql19-md] Web [!INCLUDEsssql19-md] Enterprise
[!INCLUDEssSQL16] 13.0.1601.5 Standard	[!INCLUDEsssql19-md] Enterprise [!INCLUDEsssql19-md] Standard
[!INCLUDEssSQL16] 13.0.1601.5 Web	[!INCLUDEsssql19-md] Enterprise [!INCLUDEsssql19-md] Standard [!INCLUDEsssql19-md] Web
[!INCLUDEssSQL16] 13.0.1601.5 Express	[!INCLUDEsssql19-md] Enterprise [!INCLUDEsssql19-md] Standard [!INCLUDEsssql19-md] Web [!INCLUDEsssql19-md] Express [!INCLUDEsssql19-md] Developer
[!INCLUDEssSQL16] 13.0.1601.5 Business Intelligence	[!INCLUDEsssql19-md] Enterprise
[!INCLUDEssSQL16] 13.0.1601.5 Evaluation	[!INCLUDEsssql19-md] Evaluation [!INCLUDEsssql19-md] Enterprise [!INCLUDEsssql19-md] Standard [!INCLUDEsssql19-md] Web [!INCLUDEsssql19-md] Developer
[!INCLUDEsssql17] Enterprise	[!INCLUDEsssql19-md] Enterprise
[!INCLUDEsssql17] Developer	[!INCLUDEsssql19-md] Developer [!INCLUDEsssql19-md] Standard [!INCLUDEsssql19-md] Web [!INCLUDEsssql19-md] Enterprise
[!INCLUDEsssql17] Standard	[!INCLUDEsssql19-md] Enterprise [!INCLUDEsssql19-md] Standard
[!INCLUDEsssql17] Web	[!INCLUDEsssql19-md] Enterprise [!INCLUDEsssql19-md] Standard [!INCLUDEsssql19-md] Web
[!INCLUDEsssql17] Express	[!INCLUDEsssql19-md] Enterprise [!INCLUDEsssql19-md] Standard [!INCLUDEsssql19-md] Web [!INCLUDEsssql19-md] Express [!INCLUDEsssql19-md] Developer
[!INCLUDEsssql17] Business Intelligence	[!INCLUDEsssql19-md] Enterprise
[!INCLUDEsssql17] Evaluation	[!INCLUDEsssql19-md] Evaluation [!INCLUDEsssql19-md] Enterprise [!INCLUDEsssql19-md] Standard [!INCLUDEsssql19-md] Web [!INCLUDEsssql19-md] Developer
[!INCLUDEsssql19-md] release candidate*	[!INCLUDEsssql19-md] Enterprise
[!INCLUDEsssqlv15_md] Developer	[!INCLUDEsssql19-md] Enterprise

* Microsoft support to upgrade from release candidate software is specifically for customers who participated in the Early Adopter Program.

Migrate to [!INCLUDE sssql19-md]

You can migrate databases from older versions of [!INCLUDE ssnoversion-md] to [!INCLUDE sssql19-md], as long as the source database compatibility level is 90 or higher. Databases with a compatibility level of 90 (for example, on [!INCLUDE ssversion2005-md]), are automatically upgraded to a compatibility level of 100 when migrated to [!INCLUDE sssql19-md]. If the compatibility level on the source database is 100 or higher, it will be unchanged on [!INCLUDE sssql19-md].

For information, see Azure Database Migration Guide.

The following tips and tools can help you plan and implement your migration.

• Migration tools. Migration is supported through Data Migration Assistant (DMA).

• Backup and restore. A backup taken on [!INCLUDE sskatmai-md] and later, can be restored to [!INCLUDE sssql19-md] without changing its compatibility level, as long as the database backup has a compatibility level of 100 or higher.

  Databases with a compatibility level of 90, including backups taken on [!INCLUDE ssversion2005-md], are automatically upgraded to a compatibility level of 100 when restored to [!INCLUDE sssql19-md].

• Log shipping. Log shipping is supported if the primary is running [!INCLUDE sskatmai-md] SP3 or later, or [!INCLUDE sskilimanjaro-md] SP2 or later, and the secondary is running [!INCLUDE sssql19-md].

  [!WARNING] If an automatic or manual failover happens and the [!INCLUDE sssql19-md] instance becomes primary, [!INCLUDE sskatmai-md] or [!INCLUDE sskilimanjaro-md] instance becomes secondary and cannot receive changes from primary.

• Bulk load. Tables can be bulk copied from [!INCLUDE sskatmai-md] or [!INCLUDE sskilimanjaro-md] to [!INCLUDE sssql19-md].

[!INCLUDEsssql19-md] edition upgrade

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

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

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

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

** Changing the edition of a clustered instance of [!INCLUDEsssql19-md] limited. The following scenarios aren't supported for [!INCLUDEsssql19-md] failover clusters:

• [!INCLUDEsssql19-md] Enterprise to [!INCLUDEsssql19-md] Developer, Standard, or Evaluation.

• [!INCLUDEsssql19-md] Developer to [!INCLUDEsssql19-md] Standard or Evaluation.

• [!INCLUDEsssql19-md] Standard to [!INCLUDEsssql19-md] Evaluation.

• [!INCLUDEsssql19-md] Evaluation to [!INCLUDEsssql19-md] Standard.

See also

• [Editions and supported features of [!INCLUDEsssql19-md]](../../sql-server/editions-and-components-of-sql-server-version-15.md)
• Hardware and software requirements for installing SQL Server

Next steps

• Upgrade SQL Server
• Upgrade Database Engine
• Upgrade to a Different Edition of SQL Server (Setup)