Quantcast
Channel: SQL Server High Availability and Disaster Recovery forum
Viewing all articles
Browse latest Browse all 4689

Always on listener on named instance. Do I have to specify the port while connecting a listener created on a named instance?

$
0
0

Hi all. Here again.
Scenario: I have to consolidate several physical servers with one SQL server instance install on each one. I decided to consolidate all in one server installing different named instances. In order to avoid application connection string change I had the idea of configuring different listener pointing to different alwayson group.

To meet this requests, I configured the cluster, I installed a principal SQLServer Instance and configured the alwayson groups with the required listeners.

All ok so far, alwayson is great.

So, I installed a named instance, I configured the necessary alwayson groups and the related listener but...

NOTE: The db in the principal and in the named instance have the same name.

If I connect the listener pointing the ag belonging the named instance I connect to the principal instance!

the only way I have to connect to the named instance is to specify the port that must be different from the 1433 as usual.

Anyway, why I cannot use the 1433 port if dealing with a different ip?

Listener are the following:

Named instance
10.100.21.100 :1455

Principal instance
10.100.21.50  :1433

Thankyou


Viewing all articles
Browse latest Browse all 4689

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>