Re: SQL Performance issues questions

You probably don't want to create the indexes right from Visual Explain
(VE). You might want to get the SQL CREATE INDEX statement from VE, put it
into a source file and then run it through your own change management
processes. I've learned from experience that creating an index straight
from VE leads to a lot of confusion within the dev team.

On 30 November 2017 at 17:55, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

You can create new indexes right out of VE.

You can also use iNav SQL monitors to capture production SQL statements
and run VE over them.

IIRC, binary radix indexes are regular indexes, while encoded vector
indexes (EVI) are something different.
________________________________________
From: a4g atl [a4ginatl2@xxxxxxxxx]
Sent: Thursday, November 30, 2017 11:21 AM
To: Midrange Systems Technical Discussion
Subject: Re: SQL Performance issues questions

I was using PRTSQL which did not give me enough info.

As the SELECT statements are dynamic, I ran the program and retrieved the
SQL statement from debug. I ran it in iNav with run and explain and I found
new indexes suggested which PRTSQLINF did not have. I am creating these
indexes and testing now.

What is the difference between a "regular" index which I am creating in
iNav versus a RADIX index which I see in the recommendations?

Thanks

Darryl.

--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD