Re: Interactive SQL faster than Batch SQL?

["Clare Holtham" <Clare.Holtham@xxxxxxxxxxxxxx>]

Also the optimizer looks at how much memory is in the pool where it runs. I
suspect you won't have as much memory in the batch pool as in QINTER! This
will affect the way it chooses to process the queries. You will find out
when you use debug as suggested...

cheers,

Clare


----- Original Message ----- 
From: "Pete Hall" <pbhall@xxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, April 20, 2005 11:34 PM
Subject: Re: Interactive SQL faster than Batch SQL?


> In addition to what David has stated, there are differences in the way
> the query optimizer works, depending on whether the job is interactive
> or batch, so it could develop a completely different access plan in one
> as opposed to the other. Interactive queries are theoretically optimized
> to return a screen full of information as quickly as possible, while
> batch queries are supposed to run to completion as quickly as possible.
> It doesn't always work quite that way though. The query optimizer
> program (qqqoptim) is a piece of code, I think they sentence death-row
> inmates to work on in lieu of doing the dead-man walk. It's one complex
> Q#!#:!. There will be the occasional problem. If your debug session
> doesn't turn anything up, it might be worth a call to level 1. You could
> be the problem of the week. You get a plaque for that. I have several.
>
> Pete Hall
> http://www.pbhall.us/
>
> fkany@xxxxxxxxxxxxxxxxxx wrote:
> > When I submit an SBMJOB an SQL RPG program, it takes almost an hour to
> > process.  When I manually run the SQL statements using STRSQL, the
> > processing takes about 10 minutes.
> >
> > Anyone know why?
> >
> > Thanks,
> >
> > Frank
> >
> >
> -- 
> 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.
>
>