SQL Server Performance

Reserved characters for Server, instance name?

Discussion in 'SQL Server Clustering' started by Zirco, Oct 9, 2004.

  1. Zirco New Member


    For SQL2K clustering, I have read somewhere that certain characters must be avoid in the name. Can anyone help me to summarize the guidelines for the naming convention regarding the server name and the SQL2K instance?

    Thank you very much in advance.
  2. Luis Martin Moderator

    From BOL:

    Naming Conventions
    Names must always be unique within a scope. The scope varies depending on the object. Within a repository, information model names (that is, repository type library names) cannot repeat. Within an information model, class, interface, and relationship names cannot repeat. Similarly, within an interface, property, collection, and method names cannot repeat. Also, within a collection that supports unique naming, object names cannot repeat.

    When you create a new information model, choose your names carefully. Otherwise, you may encounter name duplication problems later on if you decide to share information models. One way to avoid name confusion is by using a distinctive prefix on all of your names. An information model name provides an obvious solution. For example, if you are using the Open Information Model (OIM), you can use the subject area names such as Database Schema (or DBSchema) as a prefix.

    In addition to unique constraints, the following naming conventions apply to Repository Type Information (RTIM) objects and relationships:

    The name cannot be a reserved SQL or MIDL keyword. Generally, you should avoid any word that is reserved by a DBMS.

    Names can be a maximum of 249 characters in length.

    Any alphanumeric character can be used in the name.

    For object instance names, you can define a name that contains leading or trailing spaces. It can also be an empty string. If the name is all spaces, it is treated as an empty string.
    Spaces within a name are allowed because COM supports it. However, if you include spaces in an interface definition name, you will get an error when you subsequently define properties on that interface.


    Luis Martin

    All postings are provided “AS IS” with no warranties for accuracy.

  3. Zirco New Member


    I was thinking about the use of dash and/or underscore in the computername and/or the Database name. Because this would hinder the failover cluster installation.

    Seems like there is no restriction for SQL2K (for either server name or DB name) as long as the identifier conforms to the standards you mentioned above.

    The dash/underscore issue was for SQL Server 7 clustering, and concerned the computer name, not the DB name.

    Please correct if I am wrong.
    Thank you in advance.
  4. Argyle New Member

    I think dash is still an issue. Avoid it if possible.

Share This Page