June 21, 2006 at 4:25 pm
Hello Everyone,
I am a contractor and I am in the process of implementing a new database archive strategy, the database is quite large with almost 15GB or data created daily.
Anyone done a similar project before, how would you go about dong it, if there is a roll on and roll off period of 6 months, eg data online for 6 months, offline for the previous 6 months.
Thanks
June 21, 2006 at 5:39 pm
I'm reading your questions today and I'm finding that they're fairly general and as such it's hard to give you a definite answer. Unfortunately there's oftentimes a lot of different ways to do some things but rarely can anyone say "you should always do it *this* way".
In terms of data archiving you need to think about what kind of database it is, how you'll go about identifying old data, where/how you'd like to store it, what your archiving schedule and functions will be, how you'd like to access old data and what that recovery would be... unfortunately I don't think anyone would be wise to make specific recommendations without knowing more about your situation.
June 22, 2006 at 12:39 am
Thanks for your reply let me elaborate more on the situation.
Its a very large database, again close to a terabyte in size, because we process data daily, this is still increasing.
I would identify old date by looking at hte table name and the date it was used/processed, ef was it 8 months ago ?
Restoring it, because restores are not going to be comon, but we just need to back it up, just in case and to also free up space.
At the moment, the tables are being dumped out onto txt files then later ziped.
Any ideas would be appreciated.
Thanks
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply