>>If I put in WHERE clause an expression like UPPER(field_name) = UPPER(var_char) and my index is not UPPER(field_name) then I won't get the Rushmore optimization at all. Thus, data retrieval would be a slow process. I have tried SYS(3054,1) to check the level of optimization and there is no optimization if WHERE and INDEX expressions don't match.
>
>Maybe there is some misunderstanding in this thread? If you want to haveep index as GENERAL collate you should first SET COLLATE TO GENERAL and secondly recreate your index from scratch. Now you have GENERAL collated index which is not case sensitive.

Ed,

I think that Dmitriy was hoping that the field LIKE cExpr clause in a query wouldn't be case sensitive. Unfortunately, it appears that it is. Further, I think that this is by design. As I mentioned earlier, both SET ANSI and SET EXACT are documented as affecting the result set. SET COLLATE isn't.