#sqlhelp Q about upgrading SQL 2017 -> SQL 2019 w AGs. I thought that when doing an inplace upgrade - you upgrade the secondaries then the main - no need to break the AGs. Am I mistaken?
@SQLMonkeyNYC Some benefits of this approach are that you’re not building new clusters or dealing with multiple listeners and new listener names so you may be able to do all of the work yourself without needing support from your infrastructure team.
@SQLMonkeyNYC You can also roll in new nodes with a new OS and new version of SQL Server into your cluster. After you roll the old nodes out then upgrade your cluster functional level.
@SQLMonkeyNYC The main problem with this approach is that if your old nodes are on Windows 2016 and you want to go to Windows 2022 you’ll have to do it twice but it’s quick and easy if you’re in the cloud and you use some sort of automation.
@SQLMonkeyNYC You are risking a world of pain. I would not recommend it. M Build another cluster and either do a distributed AG or a migration. They are pretty similar.