none
isnt there going to be a problem with server name uniqueness in azure? RRS feed

  • Question

  • hi I just set up my first sql db in azure.   then  connected using ssms.   and didn't see how server name conflicts can be avoided.  are there going to be collisions in the future when folks try to give their server a name already chosen by a different company?
    Tuesday, June 11, 2019 1:50 PM

Answers

  • Azure takes care of this for you.

    The ServerName is unique - <UniqueServerName>.database.windows.net

    You can try creating a new server with the same name that you created and check this :)

    _

    If the above answer was helpful, please click “Mark as Answer” or “Up-Vote”, which might be beneficial to other community members reading this thread. 

    Wednesday, June 12, 2019 3:02 AM
    Moderator
  • Let us assume you created an Azure SQL Server by the name contoso.database.net

    Now "contoso" becomes a UniqueServerName and cannot be created again.

    If you (or anyone else) tries to create a server with the same name again, they will be presented with the below error

    Please let us know if you have further questions.

    • Marked as answer by db042190 Friday, June 21, 2019 3:43 PM
    Friday, June 14, 2019 4:24 AM
    Moderator
  • Edited for Accuracy. 

    Yes i meant what you suggested and it should have been "based in your domain". Your feedback on the possible mapping issue makes sense to me and i will add it as a discussion point while discussing this feedback! 

    I found another Feedback item where people are voting on this feature. WOuld be great to cast your vote if this maps to the feedback directly or add a new request. 

    https://feedback.azure.com/forums/217321-sql-database/suggestions/15859027-allow-dns-alias-masking-for-sql-azure-database-ser

    On the DNS Alias based on your Domain you will need to update the CNAME but still use the DNS Server name in your Logon Username. See more details in the following Stack Overflow Post: 

    https://stackoverflow.com/questions/31319074/sql-azure-aliasing-dns-name




    Thursday, June 20, 2019 8:17 PM
  • You can't use Azure DNS to buy a domain name but you can manage your DNS records in Azure using Azure DNS. For more information, see Delegate a domain to Azure DNS. Alternatively, if your Public DNS is managed by another service provided, you can use their environment to update the CName as well. 

    • Marked as answer by db042190 Friday, June 21, 2019 3:43 PM
    Friday, June 21, 2019 3:47 AM

All replies

  • Azure takes care of this for you.

    The ServerName is unique - <UniqueServerName>.database.windows.net

    You can try creating a new server with the same name that you created and check this :)

    _

    If the above answer was helpful, please click “Mark as Answer” or “Up-Vote”, which might be beneficial to other community members reading this thread. 

    Wednesday, June 12, 2019 3:02 AM
    Moderator
  • thx, I picked the server name (and use it exactly as I named it in the portal when connecting with ssms and ssis) so are u saying if I or another company try adding the same name it will be rejected? 

    I cant impersonate another company so I cant really try out what u r claiming.  so I am really looking to the forums for a clear answer.



    • Edited by db042190 Wednesday, June 12, 2019 11:26 AM spelling
    Wednesday, June 12, 2019 11:24 AM
  • Let us assume you created an Azure SQL Server by the name contoso.database.net

    Now "contoso" becomes a UniqueServerName and cannot be created again.

    If you (or anyone else) tries to create a server with the same name again, they will be presented with the below error

    Please let us know if you have further questions.

    • Marked as answer by db042190 Friday, June 21, 2019 3:43 PM
    Friday, June 14, 2019 4:24 AM
    Moderator
  • thx, that seems like its going to become a problem.  Reminds me of how folks started buying up domain names and trying to sell them to large companies.  it seems to me ther is going to be a high chance of collisions in this space.
    Friday, June 14, 2019 3:38 PM
  • Is the concern primarily around the name hygiene? Or are there more implications that you are thinking off. I ask so that the feedback can appropriately be discussed within the Azure engineering team. 

    One difference from the Domain name example is that a DB is back-end facing while a public domain name where the buy/sell happened was for s customer facing resource. 

    Maybe one possible Workaround here is to create a Unique Server Name as Kalyan showed and then use a DNS Alias to map to a custom name in your own domain. 

    Source 1: https://docs.microsoft.com/en-us/azure/sql-database/dns-alias-overview

    Source 2: https://blogs.msdn.microsoft.com/azuresqldbsupport/2018/06/05/providing-the-server-name-explicitly-in-user-names-part-2-dns-alias-for-azure-sql-database/

     
    Tuesday, June 18, 2019 1:29 AM
  • thx Aman.   I'm not sure what you mean by hygiene but in my US state alone there are 2 other S corporations that have essentially the same name as mine.  And who knows how many more exist across the US and maybe even beyond.

    My first tendency as I got started was to name mine (the server) in such a way that my company name was included in the name.  Notice Kaylan's tendency was the same.  When I was doing this it seemed to me an explanation of how conflicts are going to be avoided deserved attention.  Maybe I'm missing something.  I get that Azure will make sure they don't occur.  I dont get how customers will accept this.

     
    • Edited by db042190 Thursday, June 20, 2019 7:24 PM clarity
    Thursday, June 20, 2019 7:22 PM
  • Thanks for the additional context and feedback. We will discuss this feedback within the engineering group and also leverage our other touch points to cross reference. 

    What i meant by naming hygiene is similar to what you described i.e. conforming to a company naming schema. At this point the best possible way would be to resolve conflicts through assigning a Unique name and using a DNS Alias based on a domain your company owns to have an authoritative name that can be then used in your systems. 



    Thursday, June 20, 2019 7:53 PM
  • ok, just to be clear you mean assign a unique name that has no meaning and try again if the name was already taken?  And then within our own network use DNS to map to the unique name? 

    or are you implying use dns in some other fashion, perhaps external to our network right in Azure itself?

    I wasn't sure what you meant by "based on a domain your company owns".  maybe you meant "based in"?


    My instincts (whatever that's worth) tell me this could be a problem if someone needs to delete their server and re add it to azure.  and "one in a million" someone else takes that name in the interim.  Maybe you would tell them to add a new, rename old and then rename new?
    • Edited by db042190 Thursday, June 20, 2019 8:16 PM better idea of what im asking
    Thursday, June 20, 2019 8:03 PM
  • Edited for Accuracy. 

    Yes i meant what you suggested and it should have been "based in your domain". Your feedback on the possible mapping issue makes sense to me and i will add it as a discussion point while discussing this feedback! 

    I found another Feedback item where people are voting on this feature. WOuld be great to cast your vote if this maps to the feedback directly or add a new request. 

    https://feedback.azure.com/forums/217321-sql-database/suggestions/15859027-allow-dns-alias-masking-for-sql-azure-database-ser

    On the DNS Alias based on your Domain you will need to update the CNAME but still use the DNS Server name in your Logon Username. See more details in the following Stack Overflow Post: 

    https://stackoverflow.com/questions/31319074/sql-azure-aliasing-dns-name




    Thursday, June 20, 2019 8:17 PM
  • thx, one more thing.  some processes that need to reach these servers will surely run external to our network/domain.  so if external happens to be an azure process, is there a form of dns in azure itself?  something a company can tailor there to what we have been discussing?
    Friday, June 21, 2019 12:19 AM
  • You can't use Azure DNS to buy a domain name but you can manage your DNS records in Azure using Azure DNS. For more information, see Delegate a domain to Azure DNS. Alternatively, if your Public DNS is managed by another service provided, you can use their environment to update the CName as well. 

    • Marked as answer by db042190 Friday, June 21, 2019 3:43 PM
    Friday, June 21, 2019 3:47 AM