January 19, 2015 at 10:01 pm
Hi,
We are rolling out the use of Availability Group listeners to our SQL Server 2012 Environment which has a 2 node multi-subnet cluster. The Primary is R/W and the Secondary is a non-readable node that would be manually failed over to in a DR scenario
I have set up the AGL and asked the sysadmins to create a DNS record in both subnets with fixed IP's.
The issue I have having is that when I ask the app developers to connect to the databases using the AGL it is totally random whether the AGL resolves to the Primary or DR node - as a result that are having problems getting their apps to connect.
I was thinking of asking the sys admins to remove the DNS record in the DR subnet and then add it back in should we need to fail over - but I was thinking there must be a better way.
Would be great to hear from anyone who has the same setup,
Cheers.
January 19, 2015 at 11:12 pm
I ran into this issue and I believe we got around it by specifying 'MultiSubNetFailover=True' in the connection string when connecting to the listener.
January 20, 2015 at 8:51 am
Pending if your connection string level is recent enough that may not be possible and you will need to change RegisterAllProvidersIP to 0.
This will require DNS changes on failover*
January 20, 2015 at 4:19 pm
Thanks so much for the feedback - it has solved my issue - I will patch the .net framework where I can so we can use the 'MultiSubNetFailover=True parameter and I have also gone through the steps in the link and can confirm all is OK since I have done that.
Once again many thanks - this is a big win for me :w00t:
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply