March 29, 2016 at 8:32 am
So we are moving from our 08 R2 cluster to a new 2014 set up. Currently we have 6 named instances that 3rd party apps connect to. What would be the best way to handle that so we don't have to go out and touch all workstations? We were hoping to get away from using that many instances but if we have to we can reuse those names.
Thoughts and/or suggestions are greatly appreciated.
March 29, 2016 at 10:07 am
Cnames might work. Instance names are staying the same from old to new?
March 29, 2016 at 10:08 am
You can try WMI scripts to remotely change the connection info. How are you storing the connection information?
March 29, 2016 at 10:18 am
The plan was to not use the same names. Was thinking of trying Listner or availablity groups to try to accomplish this. Would that be possible? I know the Listener though has a limit on characters so that might not work.
March 29, 2016 at 10:19 am
TheAccidentalDBA (3/29/2016)
You can try WMI scripts to remotely change the connection info. How are you storing the connection information?
There are 35+ apps that all use different means of connecting.
March 29, 2016 at 10:27 am
murrayb3024 50692 (3/29/2016)
The plan was to not use the same names. Was thinking of trying Listner or availablity groups to try to accomplish this. Would that be possible? I know the Listener though has a limit on characters so that might not work.
Problems i can see happening:
1) Not all the 3rd party apps may work on AG.
2) You may still end up having to update things on the desktops because of name and port changes.
if you use the same instance names, you can cname the new server same as the old server as you shut down the old one.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply