Home Forums SQL Server 2008 SQL Server 2008 - General name convention for archived or historical database RE: name convention for archived or historical database

  • August 28, 2014 at 12:10 pm

    #1741711

    sqlfriends (8/28/2014)

    We have a department who has some legacy software databases no longer in use.

    But they want to keep the data and database, and build cubes for historical data anyalysis.

    Their department only has one SQL server with a couple of dbs on it.

    My question is what usually is good practice to name those historical databases.

    I just do not want to make as the original database name, but add some prefix or suffix to let people who work on this future know they are no longer production database, but just for historical records.

    so what is recommendation for those name conventions for those databases?

    Thanks,

    I wouldn't change the original database. It could break a lot of the code. Build a separate instance and put it there as it is or, better yet, create a new server for the new stuff and don't touch the old stuff at all.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)