|
Mark, without seeing the sql statement in question, it's hard to tell... how many records do you expect to process? is the statement a set-cursor and fetch? update? run the program in debug and examine the job log messages generated. this might give you a clue to your problem. rick ----original message----- Hello all, I am having a problem with query performance with embedded SQL in an RPGLE procedure. The table in question has about 2m rows. If I issue an interactive SQL statement, using the same criteria, the results are relatively quick but the same statement within an RPGLE procedure is ridiculous. The program ran for 1 1/2 hours and failed to process one detail record. Any help would be appreciated. The table in question is a saved inventory history table over which there are no indexes. Just the primary key. I'd hate to create a logical file over this thing for one procedure. Thanks, Mark
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
