Re: Index advisor (was RE: Interactive memory pool...how much to allocate per user?)

SQL indexes have a little bit more than a DDS logical. The SQE prefers
them and will often recommend creating one whose keys match a logical.

Two choices
1) Create the index in place of the logical
2) Create the index and recreate the logical, the logical will share the
access path of the index.

HTH,
Charles


On Mon, Dec 10, 2012 at 12:41 PM, Porterfield, Sean <
SPorterfield@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

Interesting stuff. It immediately informed me of a "new" SQLRPGLE program
I didn't know about. I'm not really sure of the rules the index advisor
(or SQE) uses. One suggestion on a key matches the first key in an
existing logical file that has multiple keys and no select/omit. It's odd
to me that it wouldn't just use that file. Though it does suggest "Binary
Radix" for the index type in case that makes a difference.

Some others match as well, but most I found are logicals over multiple
physical files or contain select/omit that might not match.

If it says "Estimated Index Creation Time" is 19:12:15, is that over 19
hours?
--
Sean Porterfield

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
Sent: Monday, December 10, 2012 11:28
To: Midrange Systems Technical Discussion
Subject: Re: Interactive memory pool...how much to allocate per user?

OK, that completes some of the picture. The Quadrant and Compleo are most
likely using quite a bit of SQL, as are the the stored procedures of
course. That would explain quite a bit of the *MACHINE and *BASE faulting.

With Navigator, check out the advised indexes, and see if there are some
indexes taking over about 10 seconds to build being created routinely.
Consider building them permanently. Also, the prestart jobs QSQSRVR and
QZDASOINIT should be moved into a shared pool away from *BASE. That will
help a bunch.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


This email is confidential, intended only for the named recipient(s) above
and may contain information that is privileged. If you have received this
message in error or are not the named recipient(s), please notify the
sender immediately and delete this email message from your computer as any
and all unauthorized distribution or use of this message is strictly
prohibited. Thank you.
--
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.