Re: Advised index not used but still advised

Agreed - when you set up a monitor, you select the job or jobs - never (well, hardly ever) run it over everything!! For a few minutes on a single job, no big deal. A whole week on that job, you'll get a lot of data collected, maybe. And if you use the statement processing app and run a statement and explain it, you ARE doing a DB monitor - one of the absolutely necessary tools for us, IMO.

Good luck, Rick

Vern

Charles Wilt wrote:

Rick,

I'd suggest a developer smart enough to start a monitor is smart
enough to monitor it's impact on the system.

Having said that, unless you're trying to monitor most or all jobs,
you shouldn't see an issue.

Monitoring a single job should never be a problem.

Charles




On Tue, Sep 15, 2009 at 11:43 AM, <Rick.Chevalier@xxxxxxxxxxxxxxx> wrote:

Charles,

I agree with you. Because of the differences not only in table size but system size and workload. The issue appears to be allowing developers to start database monitors. There is concern that the monitor may cause performance issues.

Rick

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Tuesday, September 15, 2009 8:02 AM
To: Midrange Systems Technical Discussion
Subject: Re: Advised index not used but still advised

Rick,

Not only will the number of records affect what the optimizer does, but the memory and CPU make a difference as well. I assume your production box is bigger than your development box. Lastly, the workload and thus the _available_ memory make a difference as well!

Unless you duplicate the hardware and workload to another environment, running VE on the production box is the only real way to tell what's going on with a query in production.

If your ops/admin team understands VE (or they want to learn it as the know the other performance tools) then perhaps you don't need VE on the production box. But if your ops/admin team don't know VE and don't usually mess with the other performance tools, then perhaps you should be the one using VE.

HTH,
Charles

On Tue, Sep 15, 2009 at 8:32 AM, <Rick.Chevalier@xxxxxxxxxxxxxxx> wrote:

Vern,

I have Visual Explain. I can't use it on our production system because I can't start a database monitor. I have been trying for at least two years to be able to do that. For example, the development or test loan master table contains 50k records but the same production table contains over four million. I think that's enough to alter the way the analyzer might handle the query.

Anyway, the part I can't find is the 'show last SQL statement' option for jobs. I don't appear to have access to work management from iNav. I do see a plan cache under the database but it is empty.

I have to admit, I don't spend much time in iNav. The occasional Visual Explain and that's all.

Rick

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vern Hamberg
Sent: Monday, September 14, 2009 6:02 PM
To: Midrange Systems Technical Discussion
Subject: Re: Advised index not used but still advised

Rick

Visual Explain is not part of work management, it's part of the database stuff - you have to have that component installed, and that might not be there yet. There still might be blockage through App Admin, however.

HTH
Vern


Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.



Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.