0

I'm a Little confused about this topic.

I know with a default instance, we can create a cluster with let's say, with the ip x.x.x.10. then automatically this IP will connect to the x.x.x.9 that is the principal. if the principal is down, it will connect to x.x.x.8 that is the secondary.

How does this work if I have a named instance? I'm having a problem that I create both instances X.X.X.36\SQLPRIMARY and X.X.X.37\SQLBACKUP. I'm trying to connect via SSMS to the X.X.X.38 That is the CLUSTERs Ip but It shows the error that the instance cannot be found. Normally with a non named instance, using that cluster IP, it points to the primary SLQ instance on that cluster.

Does the listener have this job here? I think I quiet not understand it's purpose.

  • Why are you using IPs vs dns name (name of listener with port) ? – Kin Shah Aug 23 at 15:11
  • Open the listener properties, check the port which is set for the listener. Use the [listername,Port] to connect.If you make the port as 1433 in Listener properties,then just listenername will connect. – Ramakant Dadhichi Aug 23 at 15:12
2

I'm trying to connect via SSMS to the X.X.X.38 That is the CLUSTERs Ip but It shows the error that the instance cannot be found.

Named instances, by default, don't listen on port 1433, which is required to connect without a specific port or instance name.

However Failover Cluster Instances always listen on dedicated IPs, so you can (and should) reconfigure your FCIs to listen on port 1433 using SQL Server Configuration Manager.

You can do the same thing if your instances are standalone (non-FCI), but you have to configure them to listen on specific IPs in the case you have multiple instances installed on a server. If you have a single named instance installed on each server you can simply configure it to listen on port 1433 on all IPs.

0

Normally with a non named instance, using that cluster IP, it points to the primary SLQ instance on that cluster

Usually, this managed by listener not with Cluster IP.

As i understand (from title), both instances (SQLPRIMARY and SQLBACKUP) are replicas of an Availability Group.

Normally, this group resources would be available in WSFC to have auto-fail-over capability, listener is one of them (network resource), and when we connect listener IP (along with it's port) it redirects the connection to Primary Replica. This Answer might be helpful for quick understanding on AG setup.

As confirmed already by Mr. David Browne, named instances won't listen on 1433, by default named instances listen on dynamic ports that are managed by SQL Brower service, Pls ensure the service is running, and the port UDP: 1434 open at firewall, in case if you want connect named instances directly (for some reason).

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.