http://blogs.msdn.com/b/sqlprogrammability/archive/2006/05/12/596401.aspxA typical programmer may expect that the predicates are always evaluated in the order that they are specified, but this is not true in database systems. For example, for the following clause, where col11 = 5 and convert(int, col2) = 100 programmersen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/sqlprogrammability/archive/2006/05/12/596401.aspx#9754146Mon, 15 Jun 2009 20:28:40 GMT91d46819-8472-40ad-a661-2c78acb4018c:9754146 SQL Programmability amp API Development Team Blog Predicate ordering is | debt settlement program<p>PingBack from <a rel="nofollow" target="_new" href="http://edebtsettlementprogram.info/story.php?id=24305">http://edebtsettlementprogram.info/story.php?id=24305</a></p> <img src="http://blogs.msdn.com/aggbug.aspx?PostID=9754146" width="1" height="1">http://blogs.msdn.com/b/sqlprogrammability/archive/2006/05/12/596401.aspx#602109Fri, 19 May 2006 23:24:41 GMT91d46819-8472-40ad-a661-2c78acb4018c:602109AdamMachanicOr, better, how about designing tables with properly typed columns so as to avoid bad data issues to begin with? <br><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=602109" width="1" height="1">