I didn't think I was actually blaming Microsoft. I may not be very clear when I state the deal as it appears to me. What I was trying to get at was, perhaps the reason so many folks think it is ok to use the In and Not In operators, may be its behavior in Oracle is efficient. But more to the point, I don't know how it behaves in Oracle and didn't wish to say folks were wrong if they'd had the experience in Oracle with a more efficient capability for using In and Not In.

Nice to see it in printing, that it is Or'd. Makes sense why this operator is so inefficient. Thanks for clearing it up.