April 24, 2015 at 12:04 pm
So we are going to be moving from 2005 to 2014. We have used named instances in 2005, for ex srv1\instance1, srv2\instance2... I have not really used Availability Groups up until now. The environment we are setting up is a little different with how many servers we are going to be using and how we want to do failovers. We were hoping to keep the instance names since applications call on those but not do multiple instances in the new 2014 environment. Is something like that possible? Can Availability Groups be used like instances? Can the listener? Or a way of aliasing that?
Any info is appreciated.
Thanks!
April 27, 2015 at 9:51 am
I'm not sure if I'm reading your question right, but I think you're saying you want to have only default instances when you move to SQL 2014, then create listener devices with the same names as your old instance names so that the applications can connect straight to the new instances without needing to be reconfigured? That might be possible, but it sounds a bit messy to me. Can you update your connection strings instead?
If you decide to use AlwaysOn Availability Groups for HA/DR then you can (if you want) create a listener device for each AG. Then you could connect to it as follows, using some completely made up details as an example:
- Your instance name is INSTANCE1
- Your listener device name is LISTENER1
- Your port number is 5678
You could then point connections at the listener device by connecting to LISTENER1,5678
Is that the sort of thing you mean? Effectively, connecting to the listener device is pointing at the primary node in your AG, regardless of where you fail over to. Write connections have to go to the primary, so they are usually pointed at the listener device. (Depending on your setup you may want to read from the secondaries or not, and configure your connection strings accordingly. There can be licensing implications for readable secondaries though.)
There are other settings you will need to consider for your connection strings too, including multisubnet failover and register all providers IP.
Do you definitely want to use AlwaysOn for HA/DR anyway, or are you just trying to use listener devices to find a way to avoid having to change how your applications connect? Because if it's the latter, it would be a bit like taking a sledgehammer to crack a walnut, not to mention potentially expensive, and you might want to reconsider.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply