|
When working with BPCS SQL's on a good size box I've seen an invoice runs go for 5 days on 1500 invoices. SQL in question read 900,000 recs for each invoice with no hits. I added one LF for that key/select ran in 20 minutes.Looked like it was doing *Loval Setll, Read all If to me. Size of box/LF's compiled in order for optimizer to find was important there. Early 2000 not sure if same now. Bill H -----Original Message----- From: MWalter@hanoverwire.com [mailto:MWalter@hanoverwire.com] Sent: Thursday, August 22, 2002 9:48 AM To: rpg400-l@midrange.com Subject: SQL performance 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 Mark Walter Sr. Programmer/Analyst Hanover Wire Cloth a div of CCX, Inc. mwalter@hanoverwire.com http://www.hanoverwire.com 717.637.3795 Ext.3040 _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l or email: RPG400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
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.