×
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.
The common problem is your "where" clause. Let's say your table has
1,000,000 rows. Your "where" clause returns only 1,000 rows. When ran on
the host you notice nothing. However, when ran on a client it still has
to pass each row down to the client for analysis. HUGE difference.
Multiple workarounds.
Run something like SQL2XLS to generate the excel spreadsheet on the IBM i.
Use a Scott Klement technique to generate Excel on IBM i.
Use Perl, etc.
Create a stored procedure on your IBM i that does the 'where' analysis.
Call the stored procedure from the client to get the result sets returned.
I saw a reply to something similar where there's some technique in ODBC to
have it do the 'where' processing on the host. At least that sounds
familiar.
Rob Berendt
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
