February 7, 2017 at 9:53 am
We have an environment with multiple servers, and multiple databases on each. We have applications that need to connect to particular databases, and the mapping of what database is on which server is maintained in each application. When our DBAs want to move a db to a different, or entirely new server - we need to change each application. Is there a better way? Is there something the applications can connect to that will stay the same, but will pass on the request to the db on the correct server?
February 7, 2017 at 10:01 am
Why not have a table in a database on a central server that the applications all connect to in order to get the connection strings for their respective databases? That way, everything you need to change when a database moves is in the same place.
John
February 7, 2017 at 10:40 am
That would work. We'd have to change each application to query that table to get connections strings though. Guess I was hoping for an easier way.
I read about VNN (virtual network name) at https://msdn.microsoft.com/en-us/library/hh213417.aspx . It sounds like what I'm looking for, but we don't have a cluster, "An availability group listener enables a client to connect to an availability replica without knowing the name of the physical instance of SQL Server to which the client is connecting."
February 7, 2017 at 11:49 am
I think John probably gave you a solution that in the end requires the least amount of changes. When you think about it in the scenario you have, it seems that server and database mappings would need to be maintained, updated somewhere. When doing this in a database, it seems changes would require less time/resources and have the least impact.
Sue
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply