Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Trigger on v$sql catalog table

Re: Trigger on v$sql catalog table

From: Niall Litchfield <n-litchfield_at_audit-commission.gov.uk>
Date: Fri, 11 Jul 2003 08:47:44 +0100
Message-ID: <3f0e6ba0$0$18489$ed9e5944@reading.news.pipex.net>


"db dude" <db_guy_2002_at_yahoo.com> wrote in message news:f4a8da28.0307102219.39d01c89_at_posting.google.com...
> Why is this a bad idea. Will it degrade performance or cause any other
problems?
>
> Auditing seems to degrade performance which I am trying to avoid or
lessen.

Anurag has correctly pointed out that you can't do this.

Of course auditing degrades performance, it is bound to. The way to reduce the hit is to be highly focussed in what you audit. Mostly people think they need to know everything about everything that goes on on the system. They don't.

If you could do it you solution would in any case only outperform Oracle auditing if your coding was more efficient than the code path that Oracle have put in for auditing.

-- 
Niall Litchfield
Oracle DBA
Audit Commission UK
Received on Fri Jul 11 2003 - 02:47:44 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US