RE: Monitoring software
- From: Job Miller <jobmiller@xxxxxxxxx>
- To: "'sbecker6925@xxxxxxxxx'" <sbecker6925@xxxxxxxxx>, "david.robillard@xxxxxxxxx" <david.robillard@xxxxxxxxx>, mdinh@xxxxxxxxx
- Date: Fri, 2 Jul 2010 10:44:34 -0700 (PDT)
if worst sql doesn't correlate to "bad user experience" in some front end, or
in some batch process that requires completion in a particular window, it
doesn't much matter. does it?
monitor SLA for user experience, and only dig for bad SQL when something
someone cares about starts showing up on the violation list.
That's probably a hard job for the DBA to sit back and not care about bad SQL,
but consider it liberating.
Also if you start leveraging the new auto-tune stuff, oracle will be
prioritizing the highest impact sql of the day, week, month, and automatically
generating and evaluating profiles for those statements anyway during
maintenance task windows.
that will free you up even more supposedly.
Job
--- On Fri, 7/2/10, Michael Dinh <mdinh@xxxxxxxxx> wrote:
From: Michael Dinh <mdinh@xxxxxxxxx>
Subject: RE: Monitoring software
To: "'sbecker6925@xxxxxxxxx'" <sbecker6925@xxxxxxxxx>,
"david.robillard@xxxxxxxxx" <david.robillard@xxxxxxxxx>
Cc: "Martin Bach" <development@xxxxxxxxxxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx"
<oracle-l@xxxxxxxxxxxxx>
Date: Friday, July 2, 2010, 12:44 PM
If it makes you feel any better, you are not in the boat alone.
Everyone once in a while, we go through the ritual of
identifying the top 10 worse SQL.
Then we repeat the process of identifying the top 10 worse SQL.
Notice I did not say anything about fixing, only identifying.
Michael Dinh : XIFIN : 858.436.2929
NOTICE OF CONFIDENTIALITY - This material is intended for the use
of the individual or entity to which it is addressed, and may contain
information that is privileged, confidential and exempt from disclosure under
applicable laws. BE FURTHER ADVISED THAT THIS EMAIL MAY CONTAIN PROTECTED
HEALTH INFORMATION (PHI). BY ACCEPTING THIS MESSAGE, YOU ACKNOWLEDGE THE
FOREGOING, AND AGREE AS FOLLOWS: YOU AGREE TO NOT DISCLOSE TO ANY THIRD PARTY
ANY PHI CONTAINED HEREIN, EXCEPT AS EXPRESSLY PERMITTED AND ONLY TO THE EXTENT
NECESSARY TO PERFORM YOUR OBLIGATIONS RELATING TO THE RECEIPT OF THIS
MESSAGE. If the reader of this email (and attachments) is not the
intended recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited. Please
notify the sender of the error and delete the e-mail you received. Thank you.
From:
oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Sandra Becker
Sent: Friday, July 02, 2010 9:18 AM
To: david.robillard@xxxxxxxxx
Cc: Martin Bach; oracle-l@xxxxxxxxxxxxx
Subject: Re: Monitoring software
So what do you people do when you've provided either the information and/or
tool for developers to see the performance of their code and they refuse to
look at it and insist it is up to the DBAs to tune it and make it
efficient? I also provide performance information to my VP on a
weekly basis and all other high level execs on a quarterly basis but no one
except my VP seems to take it seriously. That's the boat I'm in right now
and it seems to have a really big hole that is leaking more day by day.
--
Sandy
Transzap, Inc.
Other related posts:
