In yesterday’s post, I showed how to configure an availability group (AG) to use the
RegisterAllProvidersIP=0when you can’t get clients to connect using the
MultiSubnetFailover=trueconnection string attribute.
I mentioned that you have to make some trade-offs when you set
RegisterAllProvidersIP=0, and included this comparison:
But….when if you can eat your cake and have it, too?
In some cases, you’ll have some applications & clients that are not able to use
MultiSubnetFailover=true, and other clients that can. Perhaps you’re working on updating a bunch of legacy Java apps to move from old jTDS drivers to the current Microsoft JDBC drivers that properly support
MultiSubnetFailover=true. Parts of your codebase have been updated, and you want them to make use of the connection string attribute for fast cross-subnet failover. But other parts of your codebase are still being updated and rely on the
RegisterAllProvidersIPcluster parameter to be false. Wouldn’t it be nice to have both?
Read on to learn how.