<commercial>
Our products, insure/INDEX and insure/ANALYSIS, are positioned for just the kind of problem you bring up - how to predict what indexes to use. They take the output of the database monitor and present it in a friendly manner. There's also an SQL Optimizer piece (like Visual Explain but does more, came out before the OpsNav thing) that lets you experiment with all kinds of knobs. Index creation from the client, etc. IBM has some white papers on SQL performance that mention them, also some Teraplex success stories.


www.centerfieldtechnology.com

</commercial>

Thanks
Vern

At 05:19 AM 3/25/2004 -0800, you wrote:
That's right.  It was a surprise to me when IBM told me this little tidbit.
We have an application that was giving between 3 to 6 minute response time
after we went to V5R2.  It always had poor response but not that bad.  I
called Tech Support at IBM and was told to create an index over the file.  I
said I had an index and that is what the SQL used in it's select,  They said
no, create an SQL index.  I forget the statistic but it has to do with the
amount of data SQL will fetch when using an SQL index vs. the access path of
a logical file.  I ran the application under debug, reviewed the optimizers
suggestions and created every index suggested.  The application now gives 1
second or better response.  My problem is how to predict what index SQL will
want to use.
Bill Erhardt



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.