Skip to content

Latest commit

 

History

History
155 lines (118 loc) · 21.3 KB

File metadata and controls

155 lines (118 loc) · 21.3 KB
title Supported version and edition upgrades (SQL Server 2022)
description The supported version and edition upgrades for SQL Server 2022.
author rwestMSFT
ms.author randolphwest
ms.date 03/23/2023
ms.service sql
ms.subservice 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 2022)

[!INCLUDE SQL Server - Windows Only]

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

Pre-upgrade checklist

  • Before upgrading from one edition of [!INCLUDEsssql22-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 [!INCLUDEsssql22-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.

Unsupported scenarios

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

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

Upgrades from earlier versions to SQL Server 2022

[!INCLUDEsssql22-md] supports upgrade from the following versions of SQL Server:

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

Upgrade from Supported upgrade path
[!INCLUDEssSQL11] SP4 Enterprise [!INCLUDEsssql22-md] Enterprise
[!INCLUDEssSQL11] SP4 Developer [!INCLUDEsssql22-md] Developer

[!INCLUDEsssql22-md] Standard

[!INCLUDEsssql22-md] Web

[!INCLUDEsssql22-md] Enterprise
[!INCLUDEssSQL11] SP4 Standard [!INCLUDEsssql22-md] Enterprise

[!INCLUDEsssql22-md] Standard
[!INCLUDEssSQL11] SP4 Web [!INCLUDEsssql22-md] Enterprise

[!INCLUDEsssql22-md] Standard

[!INCLUDEsssql22-md] Web
[!INCLUDEssSQL11] SP4 Express [!INCLUDEsssql22-md] Enterprise

[!INCLUDEsssql22-md] Standard

[!INCLUDEsssql22-md] Web

[!INCLUDEsssql22-md] Express
[!INCLUDEssSQL11] SP4 Business Intelligence [!INCLUDEsssql22-md] Enterprise
[!INCLUDEssSQL11] SP4 Evaluation [!INCLUDEsssql22-md] Evaluation

[!INCLUDEsssql22-md] Enterprise

[!INCLUDEsssql22-md] Standard

[!INCLUDEsssql22-md] Web

[!INCLUDEsssql22-md] Developer
[!INCLUDEssSQL14] SP3 Enterprise [!INCLUDEsssql22-md] Enterprise
[!INCLUDEssSQL14] SP3 Developer [!INCLUDEsssql22-md] Developer

[!INCLUDEsssql22-md] Standard

[!INCLUDEsssql22-md] Web

[!INCLUDEsssql22-md] Enterprise
[!INCLUDEssSQL14] SP3 Standard [!INCLUDEsssql22-md] Enterprise

[!INCLUDEsssql22-md] Standard
[!INCLUDEssSQL14] SP3 Web [!INCLUDEsssql22-md] Enterprise

[!INCLUDEsssql22-md] Standard

[!INCLUDEsssql22-md] Web
[!INCLUDEssSQL14] SP3 Express [!INCLUDEsssql22-md] Enterprise

[!INCLUDEsssql22-md] Standard

[!INCLUDEsssql22-md] Web

[!INCLUDEsssql22-md] Express

[!INCLUDEsssql22-md] Developer
[!INCLUDEssSQL14] SP3 Business Intelligence [!INCLUDEsssql22-md] Enterprise
[!INCLUDEssSQL14] SP3 Evaluation [!INCLUDEsssql22-md] Evaluation

[!INCLUDEsssql22-md] Enterprise

[!INCLUDEsssql22-md] Standard

[!INCLUDEsssql22-md] Web

[!INCLUDEsssql22-md] Developer
[!INCLUDEssSQL16] SP3 Enterprise [!INCLUDEsssql22-md] Enterprise
[!INCLUDEssSQL16] SP3 Developer [!INCLUDEsssql22-md] Developer

[!INCLUDEsssql22-md] Standard

[!INCLUDEsssql22-md] Web

[!INCLUDEsssql22-md] Enterprise
[!INCLUDEssSQL16] SP3 Standard [!INCLUDEsssql22-md] Enterprise

[!INCLUDEsssql22-md] Standard
[!INCLUDEssSQL16] SP3 Web [!INCLUDEsssql22-md] Enterprise

[!INCLUDEsssql22-md] Standard

[!INCLUDEsssql22-md] Web
[!INCLUDEssSQL16] SP3 Express [!INCLUDEsssql22-md] Enterprise

[!INCLUDEsssql22-md] Standard

[!INCLUDEsssql22-md] Web

[!INCLUDEsssql22-md] Express

[!INCLUDEsssql22-md] Developer
[!INCLUDEssSQL16] SP3 Business Intelligence [!INCLUDEsssql22-md] Enterprise
[!INCLUDEssSQL16] SP3 Evaluation [!INCLUDEsssql22-md] Evaluation

[!INCLUDEsssql22-md] Enterprise

[!INCLUDEsssql22-md] Standard

[!INCLUDEsssql22-md] Web

[!INCLUDEsssql22-md] Developer
[!INCLUDEsssql17] Enterprise [!INCLUDEsssql22-md] Enterprise
[!INCLUDEsssql17] Developer [!INCLUDEsssql22-md] Developer

[!INCLUDEsssql22-md] Standard

[!INCLUDEsssql22-md] Web

[!INCLUDEsssql22-md] Enterprise
[!INCLUDEsssql17] Standard [!INCLUDEsssql22-md] Enterprise

[!INCLUDEsssql22-md] Standard
[!INCLUDEsssql17] Web [!INCLUDEsssql22-md] Enterprise

[!INCLUDEsssql22-md] Standard

[!INCLUDEsssql22-md] Web
[!INCLUDEsssql17] Express [!INCLUDEsssql22-md] Enterprise

[!INCLUDEsssql22-md] Standard

[!INCLUDEsssql22-md] Web

[!INCLUDEsssql22-md] Express

[!INCLUDEsssql22-md] Developer
[!INCLUDEsssql17] Business Intelligence [!INCLUDEsssql22-md] Enterprise
[!INCLUDEsssql17] Evaluation [!INCLUDEsssql22-md] Evaluation

[!INCLUDEsssql22-md] Enterprise

[!INCLUDEsssql22-md] Standard

[!INCLUDEsssql22-md] Web

[!INCLUDEsssql22-md] Developer
[!INCLUDEsssql19] Enterprise [!INCLUDEsssql22-md] Enterprise
[!INCLUDEsssql19] Developer [!INCLUDEsssql22-md] Developer

[!INCLUDEsssql22-md] Standard

[!INCLUDEsssql22-md] Web

[!INCLUDEsssql22-md] Enterprise
[!INCLUDEsssql19] Standard [!INCLUDEsssql22-md] Enterprise

[!INCLUDEsssql22-md] Standard
[!INCLUDEsssql19] Web [!INCLUDEsssql22-md] Enterprise

[!INCLUDEsssql22-md] Standard

[!INCLUDEsssql22-md] Web
[!INCLUDEsssql19] Express [!INCLUDEsssql22-md] Enterprise

[!INCLUDEsssql22-md] Standard

[!INCLUDEsssql22-md] Web

[!INCLUDEsssql22-md] Express

[!INCLUDEsssql22-md] Developer
[!INCLUDEsssql19] Business Intelligence [!INCLUDEsssql22-md] Enterprise
[!INCLUDEsssql19] Evaluation [!INCLUDEsssql22-md] Evaluation

[!INCLUDEsssql22-md] Enterprise

[!INCLUDEsssql22-md] Standard

[!INCLUDEsssql22-md] Web

[!INCLUDEsssql22-md] Developer
[!INCLUDEsssql22-md] release candidate 1 [!INCLUDEsssql22-md] Enterprise
[!INCLUDEsssql22_md] Developer [!INCLUDEsssql22-md] Enterprise

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

Migrate to SQL Server 2022

You can migrate databases from older versions of [!INCLUDE ssnoversion-md] to [!INCLUDEsssql22-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 [!INCLUDEsssql22-md]. If the compatibility level on the source database is 100 or higher, it is unchanged on [!INCLUDEsssql22-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 [!INCLUDEsql2008-md] and later, can be restored to [!INCLUDEsssql22-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 [!INCLUDEsssql22-md].

  • Log shipping. Log shipping is supported if the primary is running [!INCLUDEsql2008-md] SP3 or later, or [!INCLUDE sql2008r2-md] SP2 or later, and the secondary is running [!INCLUDEsssql22-md].

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

  • Bulk load: Tables can be bulk copied from [!INCLUDEsql2008-md] or [!INCLUDE sql2008r2-md] to [!INCLUDEsssql22-md].

SQL Server 2022 edition upgrade

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

[!INCLUDEsssql22-md] Standard

[!INCLUDEsssql22-md] Developer

[!INCLUDEsssql22-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.
[!INCLUDEsssql22-md] Standard 2 [!INCLUDEsssql22-md] Enterprise (Server+CAL or Core License)
[!INCLUDEsssql22-md] Developer 2 [!INCLUDEsssql22-md] Enterprise (Server+CAL or Core License)

[!INCLUDEsssql22-md] Web

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

[!INCLUDEsssql22-md] Standard
[!INCLUDEsssql22-md] Express 1 [!INCLUDEsssql22-md] Enterprise (Server+CAL or Core License)

[!INCLUDEsssql22-md] Developer

[!INCLUDEsssql22-md] Standard

[!INCLUDEsssql22-md] Web

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

Edition upgrade from Edition upgrade to
[!INCLUDEsssql22-md] Enterprise (Server+CAL License) 2 [!INCLUDEsssql22-md] Enterprise (Core License)
[!INCLUDEsssql22-md] Enterprise (Core License) [!INCLUDEsssql22-md] Enterprise (Server+CAL License)

1 Also applies to [!INCLUDEsssql22-md] Express with Tools and [!INCLUDEsssql22-md] Express with Advanced Services.

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

See also

Next steps