Re: SQLRPG Program performance

[rob@xxxxxxxxx]

When I look at this it looks like the following SQL was simply an 
existence check.  Since you are asking for one field from a file where you 
already know that field's value.
Maybe this above comment will turn on a thought in the SQL guru's on this 
list.  Today is a day from he!! around here.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Ahmed Yusuf <ayusuf@xxxxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
05/09/2005 05:12 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange-L <midrange-l@xxxxxxxxxxxx>
cc

Subject
SQLRPG Program performance






I have a SQLRPG program, and it has multiple SQL Statements. When I run
PRTSQLINF for this program, it shows the estimated query run time, and 
most
of them have 1second estimated run time, but one of them has 8 seconds
estimated run time.

 

Statement:-

"C+          SELECT DISTINCT PTCNTL 

C+          INTO :CNTL FROM EPTMST 

C+          WHERE PTCNTL = :SCTL03 AND 

C+          PTCMPY BETWEEN :S2LCO AND :S2HCO AND

C+          PTLOC  BETWEEN :S2LLC AND :S2HLC"

 

SQL4021  Access plan last saved on 09/05/05 at 11:53:23.


SQL4020  Estimated query run time is 8 seconds.


SQL402D  Query attributes overridden from query options file QAQQINI in
library QUSRSYS. 

SQL4017  Host variables implemented as reusable ODP.


SQL4010  Table scan access for table 1.


 

 

My question is, is this estimated time really denotes the performance of 
the
program. And if yes, how can I improve the performance of it.

 

Waiting for reply

 

AH

 

-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.