|
Tony, Under the SQL CLI interface, you can do file overrides, just before generating a result set, but I'm not sure how it might improve performance. I've noticed quite a bit of "initialization" overhead associated with SQL CLI, but runtime performance is comparable to what I get while using SQL interactively, via the STRSQL command, which has been "good enough" for me. Are you comparing initialization, or runtime performance? I've never run into a case where traditional I/O couldn't beat an SQL statement. Nathan. --- Tony Carolla <carolla@xxxxxxxxx> wrote: > I have started using Call-level interface SQL. It > seems to work as expected, > while a bit more complex than embedded. I have > noticed that SELECT > statements executed against the local DB (served on > the AS/400 the RPG > program is running on), don't seem to perform as > well as straight RPGIV. > Obviously, there is more flexibility, using ORDER > BY, JOINs, etc., but I had > hoped that the speed would be at least the same, if > not better than RPG. > > I did a non-scientific comparison of filling up a > four-field subfile, then > displaying it. No ORDER BYs, or anything, just pick > the first 9999 records, > and display them. The SQL program takes double the > time of a similar RPG > program. I know how to improve sorting/joining/IF > select statements with > indexing, but this is just straight arrival-sequence > reading. > > Has anybody else had this experience also? Can I do > file overrides that will > influence the performance of the SQL statements? > > -- > "Enter any 11-digit prime number to continue..." > "In Hebrew SQL, how do you use right() and > left()?..." - Random Thought > "If all you have is a hammer, all your problems > begin to look like nails" > -- __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
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.