Azure Devops 2022.2 – SQL 2017 support ends – Upgrading to 2022 options

Microsoft has abruptly ended support for SQL Server 2017 in Azure DevOps Server 2022.2. I am currently running my SQL databases on a SQL Server 2017 Availability Group within a WSFC (Windows Server Failover Cluster). My primary question is whether I can set up a new SQL Server 2022 cluster and migrate my databases over. Specifically, can I use the backup and restore or detach/reattach methods for migration?

I’ve come across conflicting information and have not found an official answer. Does Azure DevOps only support migrations to a server running the same version of SQL? How does this approach differ from stopping my collections and performing a rolling update?

My initial plan is to set up a new SQL Server 2022 AG (Availability Group) cluster and migrate my databases to this new cluster. Once everything is up and running, I would then update Azure DevOps from version 2022.1 to 2022.2.

Current Environment:
Azure DevOps 2022.1 on Windows Server 2019 SQL Server Database: WSFC running SQL Server 2017

Target Environment:
Azure DevOps 2022.1 on Windows Server 2019 SQL Server Database: WSFC running SQL Server 2022 on Windows Server 2022

My application server will be updated later to Azure DevOps 2022.2, and I may perform an in-place upgrade to Windows Server 2022 at that time. For now, my focus is on addressing the SQL compatibility issue.

I would greatly appreciate any insights or guidance you can provide. Thank you in advance!

I have setup the cluster so far. I haven’t performed any changes to my production just yet.