locked
referencing SQL backend of the SharePoint farm by FQDN is less stable? RRS feed

  • Question

  • Dear MSFTees,

     

    I've been told that referencing SQL backend of the SharePoint farm by FQDN is less stable than referencing it by NetBIOS name. Please share the arkane internal KB knowledge about the anticipated intermittent or permanent issues an FQDN environment might exhibit.

     

    Thank you in advance.



    • Edited by Mike Walsh FIN Tuesday, December 20, 2011 8:30 AM SL isn't a title
    • Edited by AKrasheninnikov Saturday, December 24, 2011 9:03 PM typo
    Tuesday, December 20, 2011 7:02 AM

Answers

  • Surprisingly, noone pointed out to http://www.harbar.net/articles/sp2010ups2.aspx#ups12 where the following can be found:

    After clicking Start in Services on Server, nothing happens for 20 minutes and UPS is not provisioned. No ILM Configuration steps are logged to the ULS

    This condition occurs when a Fully Qualified Name (FQDN), for example, SQLSERVER1.domain.com, or IP Address has been used as the address for the SQL Server in the SharePoint Configuration Wizard (PSConfig) when creating the Farm. UPS (amongst other things) has major issues with FQDNs and IP addresses. Don’t use them! Use a NetBIOS name (e.g. SQLSERVER1) or a SQL Server Alias when creating the farm.

    Wednesday, February 15, 2012 6:58 AM

All replies

  • Hi,

     

    I wonder where did you hear this from. I did some research, but not getting anything stating that SQL backend of the SharePoint farm by FQDN is less stable than referencing it by NetBIOS name.

     

    Thanks.


    Pengyu Zhao

    TechNet Community Support

    • Marked as answer by Pengyu Zhao Friday, December 30, 2011 2:01 AM
    • Unmarked as answer by AKrasheninnikov Sunday, January 1, 2012 6:44 PM
    Thursday, December 22, 2011 9:41 AM
  • This was included in two related cases my company had with Premier Support, but I'm trying to use every possible way to verify the information and maybe alert others if it is true. I hope it won't hurt anyone if I quote a piece: "Anyway, using FQDN was not recommended and advised against on MOSS 2007, it is now and will be in next edition of SharePoint server, as issues it can create are unpredictable and mostly untraceable." at the same time the escalation engineers both in Russia and EMEA refuse to provide a reference to specific internal or public documents where this recommendation is included. 
    Thursday, December 22, 2011 3:12 PM
  • Surprisingly, noone pointed out to http://www.harbar.net/articles/sp2010ups2.aspx#ups12 where the following can be found:

    After clicking Start in Services on Server, nothing happens for 20 minutes and UPS is not provisioned. No ILM Configuration steps are logged to the ULS

    This condition occurs when a Fully Qualified Name (FQDN), for example, SQLSERVER1.domain.com, or IP Address has been used as the address for the SQL Server in the SharePoint Configuration Wizard (PSConfig) when creating the Farm. UPS (amongst other things) has major issues with FQDNs and IP addresses. Don’t use them! Use a NetBIOS name (e.g. SQLSERVER1) or a SQL Server Alias when creating the farm.

    Wednesday, February 15, 2012 6:58 AM
  • No one probably pointed at that article because it is for SP 2010 and the forum you posted to is for pre-SP 2010 questions.

    Moderator


    SP 2010 "FAQ" (mainly useful links): http://wssv4faq.mindsharp.com/default.aspx
    WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx
    Both also have links to extensive book lists and to (free) on-line chapters

    Wednesday, February 15, 2012 9:17 AM