Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: Episode 2: the EntMgr Green Light!!
"Domenic G." <domenicg_at_hotmail.com> wrote in message
news:c7e08a19.0311091033.57531b25_at_posting.google.com...
> Running stats generates database workload also -- let's not do that
> either then because the benefit really isn't that much. I really
> don't see any change in execution plans (for the better) when stats
> are rerun more often than not.
Ever wondered why Oracle was going down the 'only analyze when the table has been subject to significant DML' route? If the execution plan really isn't changing, and performance is fine then I entirely agree with your tongue in cheek remark. Why subject your system to more work than is necessary?
I'm not entirely convinced by Oracles default definition of 10% as 'significant', but yes I suspect that our regularly scheduled analyzes are overkill. The key for me is formulating an appropriate test to help determine what 'stale' actually means for our app. With a bit of luck I can think about that whilst waiting for a few index rebuilds...
-- Niall Litchfield Oracle DBA Audit Commission UK ***************************************** Please include version and platform and SQL where applicable It makes life easier and increases the likelihood of a good answer ******************************************Received on Sun Nov 09 2003 - 14:35:20 CST
![]() |
![]() |