Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
My users are archiving many old datas.
Would it be useful executing this step after archival is complete ?
How do i know if i have to execute EXEC dbms_stats.gather_schema_stats or not?
Can i run this in business hours ?
ANy issue in over writing old statistics.
I am new and with lot of concern on how to proceed.any suggestions will be helpful
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Rule of thumbs #1
Do nothing when less than 20% of your data has changed.
Rule of thumbs #2
If your database is very small (under 20 Gig) many people just schedules a weekly job to take care of gathering statistics, most likely during the weekend.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Gathering schema stats takes long time depending on how much is the schema size and what hour of the day you are doing this. At what frequency and what sample percent is again a debatable issue. But i think you may try doing it with 25% sample and weekly basis.
Bookmarks