Re: SQL Tools and Performance

[Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

Gerald

STRSQL makes an assumption that it will return the first page of records 
quickly - "batch" type tools make the assumption that the entire set has 
to be returned before displaying anything.

In STRSQL, do you mean by "complete", that you see something on the 
screen? What happens when you put B in the control field and press 
Enter? That will make it go to the bottom, hence going through the 
entire result set.

There is also the possibility that STRSQL is at interactive run priority 
(20) and the others MIGHT be at batch run priority (50) - but that's not 
always the case.

HTH
Vern

On 3/12/2015 8:18 AM, Gerald Kern wrote:
> FYI, cross posted on Midrange and WDSCi lists as not sure where this
> question would be most appropriate.
>
> I have a relatively simple SQL statement, that when run on a green screen
> via STRSQL takes less than 3 seconds to complete. The result set contains
> about 600,000 records.
>
> However, if I use the Database Development perspective in RDi, or the SQL
> Explorer plugin in Rdi or the standalone product AQT (advanced query too,
> which supports DB2 for i), the same SQL statement takes considerably longer
> and by considerably I mean upwards of 15 minutes - if it does complete at
> all. (I like to use these tools because they offer options for exporting
> the result set to excel which is great for ad hoc requests.)
>
> Does anyone know of any tricks to improve the performance of these type of
> odbc/jdbc connections so that they might take advantage of superior SQL
> functionality available as when running sql from STRSQL?