• So should I say that it is the old way of INNER JOINing tables, that will not be supported in future versions !!

    Also, when we write "x IN (2,4,6)", optimizer converts it into "x=2 OR x=4 OR x=6", we can see it in execution plan. Does Sql store this optimized query somewhere?