|
Use the iSeries Query Optimiser to explain how your queries are being resolved, and to get access path suggestions. There are two ways (that I know of) to get at the info: 1. If you have Ops Navigator, use the Run SQL Scripts option and from there use Visual Explain. 2. In a regular iSeries session, put the job into debug mode with STRDBG (no other parameters required), then do STRSQL and run your query. The Optimiser messages will appear in the joblog. The optimiser will often give suggestions for access paths to create. Often I find that if the optimiser is not using the access paths you expect it to, then you need to look again at your query, rather than just blindly creating the suggested access path. Regards, Chris. -----Original Message----- From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of David Gibbs Sent: 16 May 2006 16:48 To: java400-l@xxxxxxxxxxxx Subject: JDBC performance suggestions for DB2 400? Folks: Does anyone have any links, or suggestions, for improving the general performance of DB2/400 via JDBC (running off the iSeries)? I'm interested mainly in adjustments that can be made without effecting the database directly (i.e., new access paths, etc). Thanks! david
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.