×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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?
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.
midrange.com
