SQL Server instance naming conventions

Posted on 2004-11-18
Last Modified: 2010-05-18
Does anyone have any suggestions for a good naming convention for SQL Server instances?

I have taken over a group of SQL Servers with mostly default names but more instances will be installed in the future.  I'm looking to distinguish between DEV, Test and Production instances.  

Apps are involved of course but I'm not sure if I should attempt to include, say, three letters that represent the app.  

Also not sure if I should include, say, three letters representing the company's name.  

Also not sure if I should include 'SQL' somewhere in there.

I've also seen variations where DBA's have included the letter 'V' for virtual and 'I' for instance.

I would like to hear some opinions about what is a good, simple and flexible naming convention.

Question by:AustinSeven
    LVL 18

    Expert Comment

    Hi Austin.   I gues from "Also not sure if I should include, say, three letters representing the company's name. "   you have identified that the key issue really is that of  "How do I name my instances so that they wont conflict with any that may be from a vendor?"

    I dont think there is any point in putting "SQL" into the name as by definition it is sql.   i also dont think there is any point in using I or V etc as a prefix,   since by definition an unnamed instance is refered to as <MachineName> and a named instance as <MachineName>\<InstanceName>   thus there is already an inbuilt distinction.

    I use named instances quite a bit.  especially with shipped out MSDE.    The approach we take is to have an initial 4 chars indicating the companyname  + '_' + a part distinguising the purpose of the instance + if required '_T' for test or '_D' for dev

    eg: (not that i work for FORD ,but)

    SERVER1\FORD_Sales_D    --Dev instance  
    SERVER1\FORD_Sales_T    -- Test instance
    SERVER1\FORD_Sales       -- live instance

    The problem is when the name is already in use.   Im afread there is no easy answer to this other than in the pre-install to verify it. and abort or use reserve instance name.

    LVL 13

    Assisted Solution

    my 2 cents

    I would not include app references in the instance name, essentially you might decide to move apps in the future and are then
    stuck with a naming reference which at that stage doesnt apply. Also SQL server is not restricted to only running 1 database
    at a time, you can have multiple db's on a server , each associated with a different app.

    THe i / v  reference might be useful.
    LVL 18

    Accepted Solution

    Do you need any more assistance with this question ?
    LVL 10

    Author Comment



    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    How to improve team productivity

    Quip adds documents, spreadsheets, and tasklists to your Slack experience
    - Elevate ideas to Quip docs
    - Share Quip docs in Slack
    - Get notified of changes to your docs
    - Available on iOS/Android/Desktop/Web
    - Online/Offline

    Let's review the features of new SQL Server 2012 (Denali CTP3). It listed as below: PERCENT_RANK(): PERCENT_RANK() function will returns the percentage value of rank of the values among its group. PERCENT_RANK() function value always in be…
    International Data Corporation (IDC) prognosticates that before the current the year gets over disbursing on IT framework products to be sent in cloud environs will be $37.1B.
    Via a live example, show how to shrink a transaction log file down to a reasonable size.
    Via a live example, show how to setup several different housekeeping processes for a SQL Server.

    759 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    12 Experts available now in Live!

    Get 1:1 Help Now