| title | Supported version and edition upgrades (SQL Server 2022 Preview) | ||||
|---|---|---|---|---|---|
| description | The supported version and edition upgrades for SQL Server 2022 Preview. | ||||
| ms.custom | |||||
| ms.date | 05/24/2022 | ||||
| ms.prod | sql | ||||
| ms.reviewer | |||||
| ms.technology | install | ||||
| ms.topic | conceptual | ||||
| helpviewer_keywords |
|
||||
| author | rwestMSFT | ||||
| ms.author | randolphwest | ||||
| monikerRange | >=sql-server-2017 |
[!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].
- Before upgrading from one edition of [!INCLUDEsssql22-md] to another, verify that the functionality you are currently using is supported in the edition to which you are 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 is a pending restart.
- Upgrade will be blocked if the Windows Installer service is not running.
-
Cross-version instances of [!INCLUDEsssql22-md] are not 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 is not supported. You cannot 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 are not published in replication. You must re-create any logins and other user objects in
master,msdb, andmodelsystem databases. -
You cannot 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:
- [!INCLUDEssSQL11] SP4 or later
- [!INCLUDEssSQL14] SP2 or later
- [!INCLUDEssSQL16] SP2 or later
- [!INCLUDEsssql17-md]
- [!INCLUDE sssql19-md]
Specific version and edition upgrade paths are not available during community technology preview releases.
You can migrate databases from older versions. For example, you can migrate databases from [!INCLUDE sskilimanjaro-md] to SQL Server 2022 Preview.
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 SQL Server 2008 or SQL Server 2008 R2 can be restored to SQL Server 2022 Preview.
-
Log shipping: Log shipping is supported if primary is running SQL Server 2008 SP3 or later, or SQL Server 2008 R2 SP2 or later, and secondary is running SQL Server 2022 Preview.
[!WARNING] If an automatic or manual failover happens and the SQL Server 2022 Preview instance becomes primary, SQL Server 2008 or SQL Server 2008 R2 instance becomes secondary and cannot receive changes from primary.
-
Bulk load: Tables can be bulk copied from SQL Server 2008 or SQL Server 2008 R2 to SQL Server 2022 Preview.