July 22, 2015 at 11:43 am
We have a bought in application written in Visual Basic 6 using ADO 2.7 to connect to SQL Server. The application has two connections strings and uses internal logic to determine which of the two connection strings connects to a read-write database. It does something as simple as trying an update that makes no changes to a very small table somewhere.
Previously this application connected to a Mirrored Database hosted on two Windows Server Failover Clusters and SQL Server 2005.
For the future the App will be connecting this application to a SQL Server 2014 Availability Group.
The Availability Group is made up of four servers, in a cluster, two at one site on Subnet A and the other two at a second site on Subnet B. The Availability Group has been given a Listener with a DNS name of AGLISTEST on port 1433 with two Static IP addresses, one for each subnet.
Our Contractor has configured the Application’s connection strings to connect to the two Static IP addresses assigned to the AG. He is of the opinion that although ADO has zero understanding of an Availability Group, at least one of the Static IP Address will translate to the Availability Group primary server because it is a Cluster Resource and so act like a Cluster IP Address on Windows Server Failover Cluster; i.e. sort of mimicking the previous configuration.
This does work and he has demonstrated it, however I can’t find any article that proves to my satisfaction this is intended behavior not something that accidentally works. If it is accidental behavior then that would be something that might stop working at an unexpected point in the future.
All the research I have found relates to connecting to the AG Listener name, and all the multi-subnet issues and Active Directory issues that go with connecting using what is a legacy client.
So; the question is, is this translation / redirection of static IP Addresses assigned to an Availability Group listener documented and safe?
July 23, 2015 at 3:52 am
ian.procter (7/22/2015)
Our Contractor has configured the Application’s connection strings to connect to the two Static IP addresses assigned to the AG.
Connecting to the DNS name would resolve any IP connection issues.
ian.procter (7/22/2015)
He is of the opinion that although ADO has zero understanding of an Availability Group
This is not entirely accurate?
More can be found here
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 23, 2015 at 7:15 am
We're using com ADO as in installed by MDAC, not ADO.Net.
July 24, 2015 at 6:00 am
This is not the most recommended configuration in consideration that we have DNS that can handle this.
Should one of the IPs timeout for some odd reason we could have unforeseen outcomes.
perhaps using the AGLISTEST group to call the IP Addresses is better if the API is capable of configuring and calling aliases. are you able to share us a screenshot of the API's available options for configurations?
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply