Feb 12, 2018 10:00:39 AM by Denny Cherry
Yep. This is actually by design; and is because listeners can be tricky little fellas. When using a SQL Server Availability Group Listener, you can see any databases on the server that is hosting the Availability Group Listener. The reason for this is because each SQL Server Availability Group Listener merely is a connection to the instance that’s hosting that Availability Group.
This is by design, and everything is working exactly as it should be.
This same rule applies to databases which aren’t protected by the availability group. If you have multiple databases protected by an Availability Group, and several databases hosted on the active server which aren’t members of the availability group and a user connects to the Availability Group listener, they’ll be able to see all the databases on the server. This also means that as the Availability Group Listener is moved from replica to replica databases will come and go as the Availability Group is moved.
Hopefully, this explains why you might be seeing things you aren’t expecting.
The post appeared first on When Using Availability Group Listeners, Why Can I See Non-AG Databases? appeared first on SQL Server with Mr. Denny.
Tags: SQL Server
Written by Denny Cherry
I am a Senior SQL Server DBA at CDW with 10 years of IT experience, mostly as a software developer building web and windows based applications (VB, VB.NET, C#, C++ and a smidge of Java). I have always found database design and set based logic interesting, so 3 years ago I took the plunge and became a DBA, soon after I discovered people would tell anyone who would listen all about the SQL Server internals. I was hooked. I have not looked back since. The things I say represent my opinion and in no way represent the views or opinions of my employer or coworkers.