Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
 Posted - 2007-11-26 : 04:44:51
|
| I'm organising archiving of data on a weekly basis . The data relates to a relatively complex game , with various data coming in from CRM on a weekly basis. Therefore the lookup tables and data inserted is always unique to that specific week.The previous games data is always deleted prior to the satart of any weeks game.There are approximately 20 tables involved , with about 1 million rows in each.From an archiving point of view , I want to maintain the integrity of the data . In these circumstances is it more efficient to retain every "game" , as a separate physical database and have a "controlling " db that I can create partitioned views ,via dynamic sql statements, or is it better to archive every table in the same db?I understand this is a general question , but I'm trying to engage some ideas based on experienced practitionersJack Vamvas--------------------Search IT jobs from multiple sources- http://www.ITjobfeed.com |
|
|
|
|
|
archiving data