SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


name convention for archived or historical database


name convention for archived or historical database

Author
Message
sqlfriends
sqlfriends
Hall of Fame
Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)

Group: General Forum Members
Points: 3862 Visits: 4017
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,
Jeff Moden
Jeff Moden
SSC Guru
SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)

Group: General Forum Members
Points: 86364 Visits: 41098
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.
If you think its expensive to hire a professional to do the job, wait until you hire an amateur. -- Red Adair

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
sqlfriends
sqlfriends
Hall of Fame
Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)

Group: General Forum Members
Points: 3862 Visits: 4017
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
Jeff Moden
Jeff Moden
SSC Guru
SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)SSC Guru (86K reputation)

Group: General Forum Members
Points: 86364 Visits: 41098
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.
If you think its expensive to hire a professional to do the job, wait until you hire an amateur. -- Red Adair

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
Eirikur Eiriksson
Eirikur Eiriksson
SSCoach
SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)

Group: General Forum Members
Points: 15160 Visits: 18599
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.
Cool
sqlfriends
sqlfriends
Hall of Fame
Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)Hall of Fame (3.9K reputation)

Group: General Forum Members
Points: 3862 Visits: 4017
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.
ScottPletcher
ScottPletcher
SSCertifiable
SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)SSCertifiable (7.9K reputation)

Group: General Forum Members
Points: 7911 Visits: 7155
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)[size=2]Prosecutor James Blackburn, in closing argument in the Fatal Vision murders trial: If in the future, you should cry a tear, cry one for them [the murder victims]. If in the future, you should say a prayer, say one for them. And if in the future, you should light a candle, light one for them.[/size]
Eirikur Eiriksson
Eirikur Eiriksson
SSCoach
SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)SSCoach (15K reputation)

Group: General Forum Members
Points: 15160 Visits: 18599
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.
Cool
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search