Printable View
Hello... I would like to get some opinions/ideas on the advantages of turning statistics off on a production database. I am currently working on an 11g instance and just surprised to find out that we do not collect stats on it.
Thanks for the inputs/ideas/advices.
Scenario #1... user complains that critical query that used to be sub-second is now taking up to four minutes to complete. How do you validate that statement and check - let's say - how many buffer_gets the query is doing now and has being doing in the past if you do not have stats?Quote:
Originally Posted by coyferrer
Scenario #2... last Monday new functionality was added to the system and now users of some well established old functionalities are complaining, specially in the 7am to 9am timeframe. How do you compare early morning work-load let's say today's vs. last Wednesday if you do not have stats?
Scenario #3... a SAN controller was upgraded and management wants to know how is this affecting I-O service levels at database side. How do you answer this question if you do not have stats?
Hi Pavb,
Thanks for your reply.
I am in the same boat as you; i firmly believe in the importance of collecting stats. What I am trying to comprehend is why would anyone NOT want to do that. The response that I got so far are the ff.:
- we know the data really well;
- when migrating the database, we had issues with the stats so we turned it off.
To me, those are not valid reasons. But then I am just a developer, not a DBA.
Thoughts?
Thanks!
Mother teached me to say nothing if I have nothing good to way so... I'm saying nothing. :)Quote:
Originally Posted by coyferrer