Creating alias on clustered instances

  • We are setting up aliases, on a clustered instance. When I set it up on the server the instance is currently running on, then the alias is fine. When I failover to another server, the alias does not show up in the Configuration Manager. Do I need to set the alias up, on all the nodes in the cluster? The instance is a named instance, and does not use the default port. That all gets configured correctly.

  • What kind of aliases are you talking about ?

    • DNS aliasses ?

      • We use these to provide a "more meaningful" server naming ( but connections should also provide Instancename or PortNo ) and give us the means to deliver a new server ( OS ) without having to modify all connections. Just modify the DNS alias and force the DNS replication.

    • SQL Client aliases

      • SQL Server Configuration Management / SQL Native Client Configuration -> settings only go for the specific computer and should  be replicated to other computers if needed
      • We avoid these due to them just being a local setting!

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • Thanks Johan. Specifically, I was referring to SQL aliases. I assumed they would need to be on all servers, so I added them to all nodes. We are using CNAMES for the DNS change.

    We do a tech refresh every 3 or 4 years. That requires updates to connection strings. This time around, when we update the strings, we are going to use an alias. That will make future changes a little easier. I read various articles about DNS aliases vs. CNAMES, but I'm not sure which way to go. Also, we will have to add the port number to the connection string. The standard was supposed to do that, but it wasn't done in some cases.

    Leonard

     

  • How do regular consumers ( users / applications ) connect ?

    If you activate sqlbrowser service on your instances, you don't need to provide the port number.

    ( of course not mandatory as it may open another attack surface )

     

     

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • SQL Browser is on for all nodes. Instances are all named. Users normally go through apps, never direct connect. We found through testing that the port number was required, even with browser running. Found a couple of articles that stated this was true, when using CNAMES.

    Leonard

  • another option is to have the instances listen to port 1433.

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

Viewing 6 posts - 1 through 5 (of 5 total)

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