AW: Advised index not used but still advised

Hi Rick,

for SQL performance analysis you'll need access to the database part of the
iSeries Navigator (not the application administration part).
In the iSeries Navigator part you'll not only find Visual Explain (which is
much more powerful than STRDBG), but also the SQL plan cache and SQL
Performance Monitors. You'll also find the index advices. If you open the
index advices it is also possible to get the SQL statements that caused this
advices (at least as long as there was no IPL).

iSeries Navigator Database is IBM's strategical product for database
creation, administration and analysis.
IMHO all programmers who work with (embedded) SQL and have to create
database objects, need to have access on the iSeries Navigator Database.

(Long ago it also took me more than one hour of discussion with the system
administrator and my manager to allow me to use the iSeries Navigator
Database).

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"

-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von
Rick.Chevalier@xxxxxxxxxxxxxxx
Gesendet: Monday, 14. September 2009 19:58
An: midrange-l@xxxxxxxxxxxx
Betreff: RE: Advised index not used but still advised

Charles,

Unfortunately, I am 'denied using application administration' for the work
management parts of iNav. Maybe our operations people can get to it for me.

Thanks for the tip.

Rick

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

Rick,

You've always got access to the statement.

If you know which job was servicing the request, and know that the request
was just issued, there's a "Show Last SQL" statement option you can use from
iNav.

Otherwise, there's the SQL Plan cache or as a last resort, start an SQL
monitor.

Once you have the statement displayed, Visual Explain will tell you all
about it including which query engine was used and why it didn't use the
indexes available.


HTH,
Charles

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.