RE: Long term AWR retention
- From: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>
- To: "mwf@xxxxxxxx" <mwf@xxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
- Date: Mon, 28 Jun 2010 08:00:17 -0700
Hi Mark,
I can think of a few possible answers:
1) Many DBAs don't have enough spare time to do capacity planning -
they're overloaded and always in firefighting mode
2) Many DBAs aren't engaged in the capacity planning process by management
- they're just told when it's time to upgrade and what kind of hardware they'll
be working with
3) Many can't or don't want to pay for hardware, Oracle licenses and other
costs of another machine for storing DBA data
4) Many production machines already have plenty of spare CPU cycles to
accommodate the load of analysis for capacity planning as long as the queries
are well written, tables are properly indexes, heavy activity is run during
off-peak times, etc.
Regards,
Brandon
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Mark W. Farnham
Why do so few people copy database metric data to a non-production machine?
(And AWR is just a start.)
Shouldn't every DBA and/or DBA team have a DBA's data warehouse? Why use
production cpu cycles to analyze anything but real time or near real time
concerns?
________________________________
Privileged/Confidential Information may be contained in this message or
attachments hereto. Please advise immediately if you or your employer do not
consent to Internet email for messages of this kind. Opinions, conclusions and
other information in this message that do not relate to the official business
of this company shall be understood as neither given nor endorsed by it.
Other related posts:
