title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | helpviewer_keywords | monikerRange | ||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Supported version and edition upgrades (SQL Server 2019) |
The supported version and edition upgrades for SQL Server 2019. |
rwestMSFT |
randolphwest |
07/25/2024 |
sql |
install |
upgrade-and-migration-article |
|
>=sql-server-2017 |
[!INCLUDE SQL Server -Windows Only]
You can upgrade from [!INCLUDE ssSQL11], [!INCLUDE ssSQL14], [!INCLUDE sssql16-md], and [!INCLUDE sssql17-md]. This article lists the supported upgrade paths from these [!INCLUDE ssNoVersion] versions, and the supported edition upgrades for [!INCLUDE sssql19-md].
-
Before upgrading from one edition of [!INCLUDE sssql19-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 [!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 sssql19-md], you must be running a supported operating system. For more information, see Hardware and Software Requirements for Installing SQL Server.
-
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 sssql19-md] aren't supported. Version numbers of the [!INCLUDE ssDE] components must be the same in an instance of [!INCLUDE sssql19-md].
-
[!INCLUDE sssql19-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
, andmodel
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 sssql19-md], you can add features by using the [!INCLUDE sssql19-md] Setup. For more information, see Add Features to an Instance of SQL Server (Setup).
Upgrades from earlier versions to [!INCLUDE sssql19-md]
[!INCLUDE sssql19-md] supports upgrade from the following versions of [!INCLUDE ssNoVersion]:
- [!INCLUDE ssSQL11] SP4 or later
- [!INCLUDE ssSQL14] SP2 or later
- [!INCLUDE ssSQL16] RTM or later
- [!INCLUDE sssql17-md]
The following table lists the supported upgrade scenarios from earlier versions of [!INCLUDE ssNoVersion] to [!INCLUDE sssql19-md].
Upgrade from | Supported upgrade path |
---|---|
[!INCLUDE ssSQL11] SP4 Enterprise | [!INCLUDE sssql19-md] Enterprise |
[!INCLUDE ssSQL11] SP4 Developer | [!INCLUDE sssql19-md] Developer [!INCLUDE sssql19-md] Standard [!INCLUDE sssql19-md] Web [!INCLUDE sssql19-md] Enterprise |
[!INCLUDE ssSQL11] SP4 Standard | [!INCLUDE sssql19-md] Enterprise [!INCLUDE sssql19-md] Standard |
[!INCLUDE ssSQL11] SP4 Web | [!INCLUDE sssql19-md] Enterprise [!INCLUDE sssql19-md] Standard [!INCLUDE sssql19-md] Web |
[!INCLUDE ssSQL11] SP4 Express | [!INCLUDE sssql19-md] Enterprise [!INCLUDE sssql19-md] Standard [!INCLUDE sssql19-md] Web [!INCLUDE sssql19-md] Express |
[!INCLUDE ssSQL11] SP4 Business Intelligence | [!INCLUDE sssql19-md] Enterprise |
[!INCLUDE ssSQL11] SP4 Evaluation | [!INCLUDE sssql19-md] Evaluation [!INCLUDE sssql19-md] Enterprise [!INCLUDE sssql19-md] Standard [!INCLUDE sssql19-md] Web [!INCLUDE sssql19-md] Developer |
[!INCLUDE ssSQL14] SP2 Enterprise | [!INCLUDE sssql19-md] Enterprise |
[!INCLUDE ssSQL14] SP2 Developer | [!INCLUDE sssql19-md] Developer [!INCLUDE sssql19-md] Standard [!INCLUDE sssql19-md] Web [!INCLUDE sssql19-md] Enterprise |
[!INCLUDE ssSQL14] SP2 Standard | [!INCLUDE sssql19-md] Enterprise [!INCLUDE sssql19-md] Standard |
[!INCLUDE ssSQL14] SP2 Web | [!INCLUDE sssql19-md] Enterprise [!INCLUDE sssql19-md] Standard [!INCLUDE sssql19-md] Web |
[!INCLUDE ssSQL14] SP2 Express | [!INCLUDE sssql19-md] Enterprise [!INCLUDE sssql19-md] Standard [!INCLUDE sssql19-md] Web [!INCLUDE sssql19-md] Express [!INCLUDE sssql19-md] Developer |
[!INCLUDE ssSQL14] SP2 Business Intelligence | [!INCLUDE sssql19-md] Enterprise |
[!INCLUDE ssSQL14] SP2 Evaluation | [!INCLUDE sssql19-md] Evaluation [!INCLUDE sssql19-md] Enterprise [!INCLUDE sssql19-md] Standard [!INCLUDE sssql19-md] Web [!INCLUDE sssql19-md] Developer |
[!INCLUDE ssSQL16] 13.0.1601.5 Enterprise | [!INCLUDE sssql19-md] Enterprise |
[!INCLUDE ssSQL16] 13.0.1601.5 Developer | [!INCLUDE sssql19-md] Developer [!INCLUDE sssql19-md] Standard [!INCLUDE sssql19-md] Web [!INCLUDE sssql19-md] Enterprise |
[!INCLUDE ssSQL16] 13.0.1601.5 Standard | [!INCLUDE sssql19-md] Enterprise [!INCLUDE sssql19-md] Standard |
[!INCLUDE ssSQL16] 13.0.1601.5 Web | [!INCLUDE sssql19-md] Enterprise [!INCLUDE sssql19-md] Standard [!INCLUDE sssql19-md] Web |
[!INCLUDE ssSQL16] 13.0.1601.5 Express | [!INCLUDE sssql19-md] Enterprise [!INCLUDE sssql19-md] Standard [!INCLUDE sssql19-md] Web [!INCLUDE sssql19-md] Express [!INCLUDE sssql19-md] Developer |
[!INCLUDE ssSQL16] 13.0.1601.5 Business Intelligence | [!INCLUDE sssql19-md] Enterprise |
[!INCLUDE ssSQL16] 13.0.1601.5 Evaluation | [!INCLUDE sssql19-md] Evaluation [!INCLUDE sssql19-md] Enterprise [!INCLUDE sssql19-md] Standard [!INCLUDE sssql19-md] Web [!INCLUDE sssql19-md] Developer |
[!INCLUDE sssql17] Enterprise | [!INCLUDE sssql19-md] Enterprise |
[!INCLUDE sssql17] Developer | [!INCLUDE sssql19-md] Developer [!INCLUDE sssql19-md] Standard [!INCLUDE sssql19-md] Web [!INCLUDE sssql19-md] Enterprise |
[!INCLUDE sssql17] Standard | [!INCLUDE sssql19-md] Enterprise [!INCLUDE sssql19-md] Standard |
[!INCLUDE sssql17] Web | [!INCLUDE sssql19-md] Enterprise [!INCLUDE sssql19-md] Standard [!INCLUDE sssql19-md] Web |
[!INCLUDE sssql17] Express | [!INCLUDE sssql19-md] Enterprise [!INCLUDE sssql19-md] Standard [!INCLUDE sssql19-md] Web [!INCLUDE sssql19-md] Express [!INCLUDE sssql19-md] Developer |
[!INCLUDE sssql17] Business Intelligence | [!INCLUDE sssql19-md] Enterprise |
[!INCLUDE sssql17] Evaluation | [!INCLUDE sssql19-md] Evaluation [!INCLUDE sssql19-md] Enterprise [!INCLUDE sssql19-md] Standard [!INCLUDE sssql19-md] Web [!INCLUDE sssql19-md] Developer |
[!INCLUDE sssql19-md] release candidate 1 | [!INCLUDE sssql19-md] Enterprise |
[!INCLUDE sssqlv15_md] Developer | [!INCLUDE sssql19-md] Enterprise |
1 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 is 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.
Tool or feature | Description |
---|---|
Migration tools | Migration is supported through Data Migration Assistant (DMA). |
Backup and restore | A backup taken on [!INCLUDE sql2008-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 sql2008-md] SP3 or later, or [!INCLUDE sql2008r2-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 sql2008-md] or [!INCLUDE sql2008r2-md] instance becomes secondary, and can't receive changes from primary. |
Bulk load | Tables can be bulk copied from [!INCLUDE sql2008-md] or [!INCLUDE sql2008r2-md] to [!INCLUDE sssql19-md]. |
[!INCLUDE sssql19-md] edition upgrade
The following table lists the supported edition upgrade scenarios in [!INCLUDE sssql19-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 sssql19-md] Enterprise (Server+CAL and Core) 3 | [!INCLUDE sssql19-md] Enterprise |
[!INCLUDE sssql19-md] Evaluation Enterprise 2, 3 | [!INCLUDE sssql19-md] Enterprise (Server+CAL or Core License) [!INCLUDE sssql19-md] Standard [!INCLUDE sssql19-md] Developer [!INCLUDE sssql19-md] Web |
[!INCLUDE sssql19-md] Standard 3 | [!INCLUDE sssql19-md] Enterprise (Server+CAL or Core License) |
[!INCLUDE sssql19-md] Developer 3 | [!INCLUDE sssql19-md] Enterprise (Server+CAL or Core License) [!INCLUDE sssql19-md] Web [!INCLUDE sssql19-md] Standard |
[!INCLUDE sssql19-md] Web | [!INCLUDE sssql19-md] Enterprise (Server+CAL or Core License) [!INCLUDE sssql19-md] Standard |
[!INCLUDE sssql19-md] Express 1 | [!INCLUDE sssql19-md] Enterprise (Server+CAL or Core License) [!INCLUDE sssql19-md] Developer [!INCLUDE sssql19-md] Standard [!INCLUDE sssql19-md] Web |
Additionally you can also perform an edition upgrade between [!INCLUDE sssql19-md] Enterprise (Server+CAL license) and [!INCLUDE sssql19-md] Enterprise (Core License):
Edition upgrade from | Edition upgrade to |
---|---|
[!INCLUDE sssql19-md] Enterprise (Server+CAL License) 3 | [!INCLUDE sssql19-md] Enterprise (Core License) |
[!INCLUDE sssql19-md] Enterprise (Core License) | [!INCLUDE sssql19-md] Enterprise (Server+CAL License) |
1 Also applies to [!INCLUDE sssql19-md] Express with Tools and [!INCLUDE sssql19-md] Express with Advanced Services.
2 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.
3 Changing the edition of a clustered instance of [!INCLUDE sssql19-md] limited. The following scenarios aren't supported for [!INCLUDE sssql19-md] failover clusters:
- [!INCLUDE sssql19-md] Enterprise to [!INCLUDE sssql19-md] Developer, Standard, or Evaluation.
- [!INCLUDE sssql19-md] Developer to [!INCLUDE sssql19-md] Standard or Evaluation.
- [!INCLUDE sssql19-md] Standard to [!INCLUDE sssql19-md] Evaluation.
- [!INCLUDE sssql19-md] Evaluation to [!INCLUDE sssql19-md] Standard.
- [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
- Upgrade SQL Server
- Upgrade Database Engine
- Upgrade to a Different Edition of SQL Server (Setup)