Re: Does Oracle Have a Way to Store Historical Changes to Records?

From: Mark Malakanov <markmal_at_rogers.com>
Date: Wed, 03 Aug 2005 21:44:56 -0400
Message-ID: <aa-dnewAxaCI7mzfRVn-sA@rogers.com>

Oh, cmon! There was no requirement on 2001 backlog. :)

Sure it is possible to create a history table and hang all kinds of triggers on a source table. It is a trivial way if people needs to keep tracking for a long time. But the app and DB should be *designed* for that.

But what if the "wish of auditing" has appeared just out of blue, will you redesign your DB for a single investigation? No. But you can "trace back" as long as your archivelog retention period allows you to do. Also some automation can be done to store "interesting" records from Log Miner views to permanent tables. And performance-wise it will be more efficient.

The retention period must be SLAed. Thus traceback audit capabilities should be mentioned as well in SLA. All requests on audit investigations that are out of a retention period must be rejected.

Frank van Bortel wrote:
> Mark Malakanov wrote:
>

>>Log Miner.
>>

>
> Are you willing to put the files online to go back to 2001,
> in 2005?!?
> In theory, a possibility. Practical use? None.
>
Received on Wed Aug 03 2005 - 20:44:56 CDT