Re: Will setting timed_statistics=TRUE create much overhead?

From: Howard J. Rogers <howardjr_at_www.com>
Date: Fri, 2 Feb 2001 08:07:05 +1100
Message-ID: <3a79cff8@news.iprimus.com.au>

The rule of thumb is that if ever switching timed statistics on causes a noticeable degradation in database performance, your database clearly was performing like an absolute dog and was in desperate need of tuning anyway (which you can't do without accurate timed statistics).

In a "normal" database, it has perhaps a 1%-2% hit on performance, tops. You wouldn't notice it.

On the other hand, since it's dynamically changeable (alter system set timed_statistics=TRUE), it's not something I'd leave switched on without good reason.

Regards
HJR <dmnwork_at_my-deja.com> wrote in message news:95bml0$g0j$1_at_nnrp1.deja.com...
>
>
> An Oracle DB monitoring product I'm using (Spotlight on Oracle) wants
> to set timed_statistics=TRUE. The product docs claim this won't create
> significant DB overhead (this is for an ORCL 8.0.5 database, which will
> be upgraded to 8.1.6 eventually).
>
> What's the real answer? I know ANALYZE TABLE COMPUTE STATISTICS
> statements can be a real drag on performance. What will happen if
> timed_statistics is turned on?
>
>
> Thanks very much.
>
> - Dana
>
>
> Sent via Deja.com
> http://www.deja.com/
Received on Thu Feb 01 2001 - 15:07:05 CST