February 7, 2019 at 4:33 pm
Am I reading this article correctly? So, with SQL 2017 we can set up AlwaysOn with no Windows Cluster and still fail over back and forth? Does anybody know how to fail over to a certain Node? For example if Node1 is primary replica and you have Node2 and Node3 as secondary replicas how do you force to failover to Node 3 and not Node 2?
Appreciate the help
February 13, 2019 at 4:24 pm
JP10 - Thursday, February 7, 2019 4:33 PMAm I reading this article correctly? So, with SQL 2017 we can set up AlwaysOn with no Windows Cluster and still fail over back and forth? Does anybody know how to fail over to a certain Node? For example if Node1 is primary replica and you have Node2 and Node3 as secondary replicas how do you force to failover to Node 3 and not Node 2?Appreciate the help
There are two different ways to failover when using read-scale availability groups both of which you are specifying the node since it's done manually. It's not a high availability solution - it's more for spreading out read-only workloads. The processes are explained in the Failover The Primary section in the following documentation:
Configure read-scale for an Always On availability group
Sue
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply