<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: String length and SARGability	</title>
	<atom:link href="https://lobsterpot.com.au/blog/2013/09/23/string-length-and-sargability/feed/" rel="self" type="application/rss+xml" />
	<link>https://lobsterpot.com.au/blog/2013/09/23/string-length-and-sargability/</link>
	<description></description>
	<lastBuildDate>Tue, 09 Mar 2021 00:11:44 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>
	<item>
		<title>
		By: Beware the width of the covering range - LobsterPot Blogs		</title>
		<link>https://lobsterpot.com.au/blog/2013/09/23/string-length-and-sargability/#comment-2389</link>

		<dc:creator><![CDATA[Beware the width of the covering range - LobsterPot Blogs]]></dc:creator>
		<pubDate>Tue, 09 Mar 2021 00:11:44 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.lobsterpot.com.au/?p=3292#comment-2389</guid>

					<description><![CDATA[[&#8230;] from datetime to date? Well, it&#039;s about being able to add a helper predicate to the mix. (This is also how LIKE works against strings.) The Query Optimizer knows that all the values must be in a certain range, so that it can seek to [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] from datetime to date? Well, it&#039;s about being able to add a helper predicate to the mix. (This is also how LIKE works against strings.) The Query Optimizer knows that all the values must be in a certain range, so that it can seek to [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Rob Farley		</title>
		<link>https://lobsterpot.com.au/blog/2013/09/23/string-length-and-sargability/#comment-2388</link>

		<dc:creator><![CDATA[Rob Farley]]></dc:creator>
		<pubDate>Mon, 23 Sep 2013 04:23:01 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.lobsterpot.com.au/?p=3292#comment-2388</guid>

					<description><![CDATA[Hi Tobi,
Skip Scans would indeed be very useful.
Rob]]></description>
			<content:encoded><![CDATA[<p>Hi Tobi,<br />
Skip Scans would indeed be very useful.<br />
Rob</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: tobi		</title>
		<link>https://lobsterpot.com.au/blog/2013/09/23/string-length-and-sargability/#comment-2387</link>

		<dc:creator><![CDATA[tobi]]></dc:creator>
		<pubDate>Sun, 22 Sep 2013 21:54:02 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.lobsterpot.com.au/?p=3292#comment-2387</guid>

					<description><![CDATA[The last example would have benefited from a skip scan (&lt;a href=&quot;https://connect.microsoft.com/SQLServer/feedback/details/695044/implement-index-skip-scan&quot; rel=&quot;nofollow ugc&quot;&gt;https://connect.microsoft.com/SQLServer/feedback/details/695044/implement-index-skip-scan&lt;/a&gt;). I see opportunities for skip scans all the time, not just with &#034;filthy&#034; type conversion.]]></description>
			<content:encoded><![CDATA[<p>The last example would have benefited from a skip scan (<a href="https://connect.microsoft.com/SQLServer/feedback/details/695044/implement-index-skip-scan" rel="nofollow ugc">https://connect.microsoft.com/SQLServer/feedback/details/695044/implement-index-skip-scan</a>). I see opportunities for skip scans all the time, not just with &quot;filthy&quot; type conversion.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
