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


  1.  Home
  2. RPG400-L
  3. December 2020

Re: RPGLE Converted into SQL having performance issue

Hi Charles

Got a " This content is blocked. Contact the site owner to fix the issue "
when clicking the link
Is it only me ?

Gad




date: Tue, 15 Dec 2020 08:20:13 -0700
from: Charles Wilt <charles.wilt@xxxxxxxxx>
subject: Re: RPGLE Converted into SQL having performance issue

Not really surprising, you've replaced one access method with another that
has more overhead.

You can't simply replace RPG 1 record-at-time with SQL 1 record-at-time.
Better off to stick with RPG.

Used properly, SQL is faster than RPG. But you have to use it properly;
which means working with SETS of records.

- unless there's no other option, don't use cursors. (Display & printing
they are required)
- if using a cursor, read in blocks of records (100+)

You might find this presentation I gave a few years ago helpful..

https://www.linkedin.com/posts/charles-wilt-2a4a303_sql-for-the-rpg-developer-activity-6641756015354355712-woZR

Charles

**********************************


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.