SQL Server Performance

SQL Server name

Discussion in 'SQL Server Clustering' started by franco, Apr 2, 2004.

  1. franco New Member

    We installed SQL Server 2K and SP3a on a new Cluster with Windows Server 2003.
    This is a single instance Sql Server installation.
    The virtual server name is VSRVSQL.
    At the time the installation setup asked for the name of the instance we cleared the default check and we choose the same name of the virtual server,VSRVSQL, so we and up in having a named instance and not a default instance.
    Now in EM we see VSRVSQL/VSRVSQL and the result of sp_helpserver is VSRVSQL/VSRVSQL.

    Is this correct or it better to have a default instance in place of the named one?

    Please advise.

  2. bradmcgehee New Member

    I always use a default instance, although it is not required. Default instances are a, in my opinion, a little easier to keep straight in your mind.

    Brad M. McGehee, MVP
  3. Luis Martin Moderator

    Agree with Brad, the razon is: when you choise non default instance, SQL name it: ServerNameInstanceName.

    Luis Martin
  4. franco New Member

    Thank you all for your quick reply.
    I suppose there are no ways to come back to a default instance right?
    If I understand correctly the difference between is that the connection to SQL Server is made thru Servername/NamedInstance.
    Are there any other things that I am to be aware of?
    Any help is really appreciated.
    Kind regards.

  5. Argyle New Member

    Clients accessing the server need MDAC 2.6 or higher I think to be able to understand the named instance format (MyServerinstance). If they have lower MDAC, you need to create aliases on each client pointing to a standard name like "MyServer".<br /><br />Having the server named VSRVSQLVSRVSQL sounds like asking for trouble <img src='/community/emoticons/emotion-5.gif' alt=';)' />

Share This Page