RE: SQL, Unions, Indexes & Logical Files.

["Elvis Budimlic" <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx>]

I figured LANGIDSHR would be considered 'translation' by DB2 engine.
Perhaps it would simply mean that index would not be used by SQE but CQE
would use it and that's what his query will end up using anyway.

I agree with you on overemphasis of CQE vs SQE from the functional
perspective.  I only brought it up for the DBA types that need/like to
concern themselves with such detail.  Truth is, both engines can be tuned to
perform well, either by building the appropriate index and/or changing SQL
statement slightly.

Elvis

Celebrating 10-Years of SQL Performance Excellence

-----Original Message-----
Subject: RE: SQL, Unions, Indexes & Logical Files.

> Either by forcing 'a' to upper in the table,
> or forcing the comparison value to be the match the case in 'a'?
> I'd recommend using *LANGIDSHR (shared weight) indexes to avoid use of
UPPER
> but that'll probably cause it to go CQE as well.  

LANGIDSHR would seem the logical choice to me too, but why do you feel
that would force it down CQE?

Also, and you say this too, I think we may be getting to tied up in
caring about CQE vs. SQE. Both will return the correct result. Caring
about which engine you're using should be left to the bitter end, both
because it's simply a performance issue, and because the longer you wait
to worry about it the more likely it is you'll use SQE since everything
is headed there anyway.

-Walden