

Also, because a connection can fail because of an availability group failover, you should implement connection retry logic, retrying a failed connection until it reconnects. Increasing connection timeout and implementing connection retry logic will increase the probability that an application will connect to an availability group. Rest of the connection attempts follow the same logic as in the multiSubnetFailover feature.

#Tune dbvisualizer driver#
If the first attempt fails, the driver tries to connect to all IP addresses in parallel until the timeout expires, discarding any pending connection attempts when one of them succeeds. When transparentNetworkIPResolution is true, the driver attempts to connect to the first IP address available. For more details, see the sections below.īeginning in version 6.0 of the Microsoft JDBC Driver for SQL Server, a new connection property transparentNetworkIPResolution (TNIR) is added for transparent connection to Always On availability groups or to a server that has multiple IP addresses associated. Use applicationIntent to declare the application workload type.
