Re: How to force sql CQE instead of SQE V6r1

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

Oh, yeah - I think it's safe to say, SQE needs good indexes. Your best 
payoff may come from running Visual Explain, to get index advice.

On 3/30/2012 8:06 AM, Vern Hamberg wrote:
> Hi Franz
>
> I'm with Tommy - not sure how it could be broken. Does it give incorrect
> results? Does it have a different sort order? Does it take too long?
>
> In other words, just HOW is it broken?
>
> If you are not getting the same results, that is a definite bug, and you
> need to call IBM RIGHT NOW! =-O
>
> Vern
>
> On 3/30/2012 7:30 AM, Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx wrote:
> > I'm not sure why you would have to rely on CQE?  They are 2 different
> > query engines but the results are the same...just faster with SQE.  I'm
> > just not sure how this would break your apps.  Anyway you can update
> > QAQQINI where QQPARM='IGNORE_DERIVED_INDEX' and set it to *NO
> >
> >
> >
> > From:<franz400@xxxxxxxxxxxx>
> > To:     midrange-l@xxxxxxxxxxxx,
> > Date:   03/30/2012 06:59 AM
> > Subject:        How to force sql CQE instead of SQE V6r1
> > Sent by:        midrange-l-bounces@xxxxxxxxxxxx
> >
> >
> >
> > Loaded recent ptfs&   DB2 group. v6r1
> > Now many that used to go thru CQE using SQE.
> > This broke some apps&   need a quick way to
> > get a production app to use CQE.
> > These are Windows client .net and some of the sql joins
> > are huge and ugly.
> > Have no maintenance window to back down.
> > Specify logical file in sql no longer forces CQE.
> > Jim