name convention for archived or historical database

  • 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,

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

  • 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

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

  • Quick thought, my preferred approach would be a named SQL Server instance, normally SERVERNAME_OLD. Kind of in line with Jeff's suggestion. Reason being that normally there are more than one database "related" being retired.

    😎

  • But sometimes those databases need to work with different SQL server versions.

    For example some retired db is at version 2000 and only works with 2000, some with 2005 etc.

    So only one instance cannot meet the requirment.

  • I use "__Archive" (double underscore) for those tables.

    I also maintain its structure to match the original table. That is, if the main table changes, I make the same changes in the archive table. Basically, I want a SELECT * UNION ALL between the two tables to always work.

    SQL DBA,SQL Server MVP(07, 08, 09) A socialist is someone who will give you the shirt off *someone else's* back.

  • sqlfriends (8/28/2014)


    But sometimes those databases need to work with different SQL server versions.

    For example some retired db is at version 2000 and only works with 2000, some with 2005 etc.

    So only one instance cannot meet the requirment.

    In my experience, most of the time the lowest compatibility mode is sufficient. Hardly ever have I had problem unless one is supporting 7.0 or earlier.

    😎

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply