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