Archiving Data.
-
Some of the tables in our OLTP database grow by 100,000 records a day. I am thinking of archiving data that is more than 2 weeks old into an archive database.
My question is: If I create the same structure for the archive database as I have for the OLTP database, is it ok to not have referential integrity constraints turned ON in the Archive database as I'll be loading data into this database from the oltp database by running a job every night. It will be easier to not to have to worry about the sequence in which the table loading takes place. Is it common to not have any Referential Integrity in Archive databases?
Thanks.
-
I'd say that depends on you, or rather your customer.
Is it OK to have the risk of getting 'incorrect' data? Even if the risk is minimal, it is still there, so you need to ask the question. An alternative could be to do a check after the loading to see if anything seems wrong, and if so then take action against it. You could also have referential integrity turned ON and just 'shut it off' for the import, then try to turn it ONN again and take action if this fails.
--
Chris Hedgate @ Apptus Technologies (http://www.apptus.se)
-
Thanks.
-
I'd agree. Depends if you need it. You could also denormalize and include some of the FK stuff into the table.
Steve Jones
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply