<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Implied Predicates and Query Hints</title><link>http://blogs.msdn.com/craigfr/archive/2009/04/28/implied-predicates-and-query-hints.aspx</link><description>In this post, I want to take a look at how two seemingly unrelated features of SQL Server can interact to cause a problem. The idea for this post came from a question submitted by a reader. Let's begin. Consider the following trivial schema and query:</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Implied Predicates and Query Hints</title><link>http://blogs.msdn.com/craigfr/archive/2009/04/28/implied-predicates-and-query-hints.aspx#9583520</link><pubDate>Sat, 02 May 2009 11:25:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9583520</guid><dc:creator>dbalashov</dc:creator><description>&lt;p&gt;Big thanks for your essential posts! It's very useful information for SQL developers. I set label &amp;quot;IMPORTANT&amp;quot; for each your article in my Outlook :))&lt;/p&gt;
</description></item></channel></rss>