Nope, It's no that I don't understand. I do truly, I've done this a number of times before where I've renamed a traditional FCI. I understand the computer objects that the AG listener uses. I understand what that would mean to change that. I tried to simplify the environment to make it easier to ask the question and probably did a poor job of that. I'm not planning on adding a new object with the same name as one of the old ones, or at least not until the old name has been renamed.
Let's not get hung up on the names of the objects.
Can I make a connection to SQL2\MyInstance when the ag listener is named SQL2 and have it connect to a database (DB1) that lives on MyNewServer(DefaultInstance) - Primary replica and MyOtherNewServer(Myinstance) - Secondary Replica
Will the AG Listener and/or SQLBrowser be smart enough to ignore the instance name and just make the connection? I'm assuming not, but I've been unable to find any information about AG Listeners with instances names, which is why I'm asking.
The reason I'd like to avoid changing the connection strings is over 100 applications on various app servers, including third party vendors that I'd need to involve, connecting to a few hundred databases across 4 instances.
While yes, I get that changing a connection string is minimal, changing connection strings on many servers, which would need to be done by other teams (server admins, programmers etc), including outside vendors is not a small undertaking and the time/cost likely wouldn't be approved by management.
If that would be required I'd probably just stick with the existing traditional FCI infrastructure. This is currently a test environment and we're evaluating what it would mean if we wanted to start using AG's as a means of migrating some of these workloads to Azure MI etc.
To help us help you read this[/url]For better help with performance problems please read this[/url]