Re: Archiving data into another database

Luc,

I work with a custom-created solution for this for a specific in-house application. The problem with most archiving solutions is that, well, disk keeps getting cheaper so the value of archiving isn't what you might think it to be. If you work with an application that does a lot of full-table scans, and you can't fix that, then definitely consider an archiving solution.

I would first consider Oracle partitioning. You can make partitions read-only, transport them to other databases, etc. Lots of neat stuff. There are commercial archiving products you can investigate.

The real problem is that Oracle is a relational database, and therefore you need to understand the relationships in order to archive the data.

Archiving looks a lot more attractive in theory than in practice. Often when it is most strongly considered is when an upgrade is coming and it doesn't look like you can convert or move all the data in a reasonable amount of downtime. Archiving can help this situation. Purging data can help even more and should be considered before archiving.

Dennis Williams

--
http://www.freelists.org/webpage/oracle-l