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:55 pm

    #1741729

    sqlfriends (8/28/2014)

    Thanks, Jeff.

    These databases no longer has front end, their new versions are already upgraded to something new and have diffrent database names.

    These are only kept for data analysis purpose, we will build SSAS cubes from them.

    The reason I thought to rename to something new - just add a suffix for exampel, is for DBAs or whoever manages the server, they later know these are no longer production databases, but just kept for historical records and for analysis purpose.

    They are all actually small databases for some old applications.

    Currently we don't have budget to buy another server for this purpose. We will use the existing server that only has two produciton databases.

    Thanks

    If the code in the databases has the mistake of 3 or 4 part naming in it, such name changes will break the database code. That could, of course, be repaired as you come upon it.

    I use an _Archive suffix on archive databases but that's not what this is. This is a deactiviation and I typically add an _OLD_YYYYMMDD suffix where the YYYYMMDD is the date that the database was officially declared to be "dead".

    --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)