Hello All,
I am looking to upgrade our SQL 2012 HADR Availability Group (3 servers) to SQL 2017. On a Test system all went well but a concern was found. I had 6 - 80 GB and 1 - 750 GB databases running. On failover after the upgrade it took approximately 10 minutes to upgrade the databases, not recover from choppy logs. The same amount of time was noticed on all three failovers. Our SaaS rows that will be upgraded contains ~250 databases and most are 300 GB - 1.5 TB. I extrapolated that it would take 18 hours just to failover three times. Does this seem right? An in-place/rolling upgrade is not my first choice and I am being asked to determine if we can make it work, 18 hours plus software upgrade is unacceptable.
Charlie
I am looking to upgrade our SQL 2012 HADR Availability Group (3 servers) to SQL 2017. On a Test system all went well but a concern was found. I had 6 - 80 GB and 1 - 750 GB databases running. On failover after the upgrade it took approximately 10 minutes to upgrade the databases, not recover from choppy logs. The same amount of time was noticed on all three failovers. Our SaaS rows that will be upgraded contains ~250 databases and most are 300 GB - 1.5 TB. I extrapolated that it would take 18 hours just to failover three times. Does this seem right? An in-place/rolling upgrade is not my first choice and I am being asked to determine if we can make it work, 18 hours plus software upgrade is unacceptable.
Charlie