Skip to main content
Database Administrators

Return to Question

small spell correction and new tags
Source Link
edit approved Oct 30, 2019 at 16:48
Shekar Kola
edit approved Oct 30, 2019 at 16:48
Shekar Kola
  • 2.4k
  • 2
  • 10
  • 24

I'm not sure quite how to word this, but I am looking for anything a DBA can do (things outside of changing code in the application) to reduce the impact to users when an AG fails over.

We have a 2 node AG running SQL 2016 SP2 CU10 in sychronoussynchronous commit mode, connecting with a listener.

whatWhat controls the switching of connections to the new primary node? is there a way to accelerate the switch? Anything in the connection string, AG settings, changing timeouts, etc. that would help make the switch faster for users?

I'm not sure quite how to word this, but I am looking for anything a DBA can do (things outside of changing code in the application) to reduce the impact to users when an AG fails over.

We have a 2 node AG running SQL 2016 SP2 CU10 in sychronous commit, connecting with a listener.

what controls the switching of connections to the new primary node? is there a way to accelerate the switch? Anything in the connection string, AG settings, changing timeouts, etc. that would help make the switch faster for users?

I'm not sure quite how to word this, but I am looking for anything a DBA can do (things outside of changing code in the application) to reduce the impact to users when an AG fails over.

We have a 2 node AG running SQL 2016 SP2 CU10 in synchronous commit mode, connecting with a listener.

What controls the switching of connections to the new primary node? is there a way to accelerate the switch? Anything in the connection string, AG settings, changing timeouts, etc. that would help make the switch faster for users?

Source Link
DBA Greg14
DBA Greg14
  • 255
  • 3
  • 18

what happens to user connections when an AG fails over?

I'm not sure quite how to word this, but I am looking for anything a DBA can do (things outside of changing code in the application) to reduce the impact to users when an AG fails over.

We have a 2 node AG running SQL 2016 SP2 CU10 in sychronous commit, connecting with a listener.

what controls the switching of connections to the new primary node? is there a way to accelerate the switch? Anything in the connection string, AG settings, changing timeouts, etc. that would help make the switch faster for users?