Skip to content

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

Latest commit

 

History

History
83 lines (57 loc) · 7.43 KB

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

File metadata and controls

83 lines (57 loc) · 7.43 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 05/25/2022
ms.prod sql
ms.technology install
ms.topic conceptual
ms.custom event-tier1-build-2022
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 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 [!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 [!INCLUDEsssql22-md]

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

Specific version and edition upgrade paths aren't available during community technology preview releases.

Migrate to [!INCLUDEsssql22-md]

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 will be 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 [!INCLUDE sskatmai-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 [!INCLUDE sskatmai-md] SP3 or later, or [!INCLUDE sskilimanjaro-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, [!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 [!INCLUDEsssql22-md].

See also

Next steps