Well, to know if something has happened to a database object implies
some kind of monitoring. To more details you want to know about the
change, the more monitoring needs to be done. Auditing would give you
some of the basics. Triggers would work if you can live with the
overhead. How much overhead? Well, how much of the changes would you
like to capture? You need not implement this yourself though. If you
would really like to capture the change in details, check out Change
Data Capture. CDC is most useful in a database warehouse environment
when you need to update your warehouse regularly with the "delta" from
the data source.
Bob Kosman <kos_at_dtransform.com> wrote in message news:<1103_1027224714_at_netnews.attbi.com>...
> [For Oracle 8 and beyond:]
> Does anyone know of any way to detect that a row in a table has
> changed - that is, has been added or updated WITHOUT putting a
> trigger on the table? I had hoped that one of the data dictionary
> tuples might have such but have been able to find one.
>
> And failing this, just how much Oracle system overhead might there
> be if I did put add/update/delete triggers on all the tables for
> which I have an interest?
>
> Thanks.
>
> Kos.
Received on Thu Jul 25 2002 - 12:43:08 CDT
