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?