Upgrading an Always on Availability Group two node from SQLServer 2016 to 2019

  • I'm looking for best practice here and these are Azure VMs by the way. My idea is to create two new Azure VM SQL Servers running SQL Server 2019 and introduce these two new servers to the existing AG. Once the databases have been seeded on the two new nodes running SQL Server 2019 the old existing two nodes can be removed from the AG.

  • That's the way I would do it.

    Set the new 2019 to ASYNC manual failover, so that things don't failover before you're ready.

    Then when the time comes, set to sync, fail them over and evict the 2016 replicas.

  • Its not clear what OS your 2016 SQL servers are running, but if they are not 2019, be sure to upgrade the cluster functional level when you are done, it is easy to forget. I haven't noticed much difference going from 2016 to 2019 clusters, but 2012 r2 to 2016 was dramatic in how much more reliable/tolerant of OS problems it was.

  • Thanks!


  • We will be upgrading the OS to 2019. Thanks for you help!

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply