Connect to clustered instances without port

  • damien.albiez 19078

    SSC Enthusiast

    Points: 131

    I am sure I could do this previous versions.  Clustered (wsfc) Sql 2017,  I can connect to the default instance without port (ie clustered name resource) but not with additional instances.  I must use [clusterinstancename],[port].
    Is it possible to do without port, ie. connect directly to the name resource?  I have been trying now for a week without luck.

  • Jeffrey Williams 3188

    SSC Guru

    Points: 87951

    Is the instance setup as an FCI (failover cluster instance) - or AlwaysOn?

    When installing an instance for FCI - the clustered resource will have an IP address and domain name assigned in DNS.   That name is what you reference when accessing that instance in the cluster.  If you are installing standalone instances that are built as AlwaysOn availability groups - then you need to create an IP address and name in DNS and add that as a listener in the AlwaysOn configuration.  You then reference the instance using the listener name or IP address.

    For either configuration - you also need to have SQL Browser running and not disabled.

    [font="Verdana"]Jeffrey Williams
    Problems are opportunities brilliantly disguised as insurmountable obstacles.

    How to post questions to get better answers faster[/url]
    Managing Transaction Logs[/url]
    [/font]

  • damien.albiez 19078

    SSC Enthusiast

    Points: 131

    Thanks Jeffery, its a 2 node FCI. Sql browser enabled and running on both nodes. Failover seamless, for the default and 4 named instances installed. Default instance accessible without port, just can't manage it for the named instances. I can only get to them using either nameresource\instancename OR nameresource,port.

    This is all related to a Sql hardware refresh, a load of applications and connection strings that I would rather leave as is.
    Cheers
    Damien.

  • John Mitchell-245523

    SSC Guru

    Points: 148218

    Damien

    Are you supplying the instance name as well - VIRTUALSERVERNAME\INSTANCENAME?

    John

  • damien.albiez 19078

    SSC Enthusiast

    Points: 131

    For the example I am discussing:

    Clustered name resource: reporting
    Instance name: RO
    Port 1436.

    These work:
    reporting\ro
    reporting,1436

    My goal is to use "reporting" only in the connections strings.

  • John Mitchell-245523

    SSC Guru

    Points: 148218

    No, that won't work.  You could set up an alias, but I think you'd have to do that on every client computer.

    John

  • damien.albiez 19078

    SSC Enthusiast

    Points: 131

    Ok thanks John.  I will keep trying!

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply