RE: Keeping deleted records
- From: "Kerber, Andrew W." <Andrew.Kerber@xxxxxxx>
- To: wbfergus@xxxxxxxxx, "oracle-l" <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 9 Aug 2007 12:27:52 -0500
Come to think about it though, if its only 35 or so tables, it wouldn't
be hard to write sql to generate the triggers to copy rows over to a
second schema as they are deleted or updated in the first schema. That
might just be the simplest and quickest.
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Bill Ferguson
Sent: Thursday, August 09, 2007 11:31 AM
To: oracle-l
Subject: Keeping deleted records
Hi all,
My management wants to keep a copy of all deleted records for historical
purposes, in case somebody decides at a later point that the deletion
was a mistake. This happens about once a year for probably a dozen or so
records.
The data structure is about 35 tables consisting of one master table
with children attached to it. Only two of the child tables have their
own children. This primarily a scientific record type database, of known
worldwide mineral deposits, so the volume of transactions is fairly low,
compared to what most of you are used to dealing with. I might have a
couple hundred transactions per day on a busy day.
I'm kind of torn between two approaches. The first approach is to
basically create a duplicate schema that contains blank table
structures, and as records are deleted, move them over to the "deletes"
schema and then delete them from production. This will entail of bunch
of redesign though on all of the triggers and others constraints in the
new schema.
The second approach would be to have the "deletes" schema be a copy of
everything currently in the production schema, and then as new records
are added, add them to the "deletes" schema, and if they're deleted,
then I don't have to do anything. This approach though would entail the
reworki9ng of all of the existing triggers in the production schema.
Either way, management hasn't said what kind of tracking (if any) that
they want for updates. It seems that they'd probably want that as well,
so if a production record was updated, the new version of the record
would be copied over to the "deletes" schema.
Anybody else ever run across this kind of requirement before and have
any ideas or suggestions on the best/easiest way to handle it?
RMAN backups would really be a pain, as the deletes could have occured
at any time and over a huge period of time as well.
Thanks.
--
-- Bill Ferguson
------------------------------------------------------------------------------
NOTICE: This electronic mail message and any attached files are confidential.
The information is exclusively for the use of the individual or entity intended
as the recipient. If you are not the intended recipient, any use, copying,
printing, reviewing, retention, disclosure, distribution or forwarding of the
message or any attached file is not authorized and is strictly prohibited. If
you have received this electronic mail message in error, please advise the
sender by reply electronic mail immediately and permanently delete the original
transmission, any attachments and any copies of this message from your computer
system. Thank you.
==============================================================================
Other related posts:
