× 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.


  • Subject: Question about SQL performance vs. RPGLE performance
  • From: dmosley@xxxxxxxxxx
  • Date: Mon, 11 Jun 2001 10:32:16 -0400


I'm curious.  I've seen performance results of SQL vs RPG,  when using
thousands of records.  But I'm just curious if there is a signifigant
performance difference when accessing only one record.

Heres my scenario :

I've created a *SRVPGM program(with multiple procedure calls) that will
access a database record, and do what ever with it.
- Some of the Procedure calls are to @dspXX0003F, @addXX0003F,
@dltXX0003FRrnDsp, @rtvXX0003FRrn, etc.....
(XX0003F is the file name)

And so what I've done rather than using CHAINS, EXCEPTS, WRITES, I've
replaced them with embedded SQLs.  The performance appears to be the same,
except for the first access, maybe a couple of seconds to prepare, but
after that, it flies.

This is all in test, and I was curious if anyone else performs database
maintenance/access like this, and if so how's the performance.


David L. Mosley, Jr.
Systems Analyst
2000 CentreGreen Way
Suite 250
Cary, NC 27513




+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.