|
> using dynamic SQL which for this > purpose (IMO would perform very > poorly...)I strongly suggest that the original poster try the dynamic SQL before throwing it out as a poor performer. It may run pitifully slow too, but you just don't know until you try.
What performs badly on my machine with my dataset may scream on yours, and vice versa. SQL is very unlike traditional RPG I/O because of the optimiser, which makes sweeping statements about SQL performance problematic at best.
--buck
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.