<?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: A CASE study in SARGability	</title>
	<atom:link href="https://lobsterpot.com.au/blog/2010/02/02/a-case-study-in-sargability/feed/" rel="self" type="application/rss+xml" />
	<link>https://lobsterpot.com.au/blog/2010/02/02/a-case-study-in-sargability/</link>
	<description></description>
	<lastBuildDate>Tue, 02 Feb 2010 18:57:32 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.3</generator>
	<item>
		<title>
		By: Rob Farley		</title>
		<link>https://lobsterpot.com.au/blog/2010/02/02/a-case-study-in-sargability/#comment-791</link>

		<dc:creator><![CDATA[Rob Farley]]></dc:creator>
		<pubDate>Tue, 02 Feb 2010 18:57:32 +0000</pubDate>
		<guid isPermaLink="false">/blogs/robfarley/archive/2010/02/02/a-case-study-in-sargability.aspx#comment-791</guid>

					<description><![CDATA[Hi Jez – yes, you can do stuff to help speed up queries (like indexed computed columns. But this piece is looking at SARGability of ordinary columns with ordinary indexes.]]></description>
			<content:encoded><![CDATA[<p>Hi Jez – yes, you can do stuff to help speed up queries (like indexed computed columns. But this piece is looking at SARGability of ordinary columns with ordinary indexes.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jeremy Huppatz		</title>
		<link>https://lobsterpot.com.au/blog/2010/02/02/a-case-study-in-sargability/#comment-790</link>

		<dc:creator><![CDATA[Jeremy Huppatz]]></dc:creator>
		<pubDate>Mon, 01 Feb 2010 09:52:05 +0000</pubDate>
		<guid isPermaLink="false">/blogs/robfarley/archive/2010/02/02/a-case-study-in-sargability.aspx#comment-790</guid>

					<description><![CDATA[Hmm… I wonder if you could do something like add a computed column that basically gives you the reverse of ‘Farley’, index the computed column, then do your search on REVERSE(‘%arley’) – might have to have a play.

That said – isn’t this something that gets fixed to some degree by using full text search?

Cheers

Jez]]></description>
			<content:encoded><![CDATA[<p>Hmm… I wonder if you could do something like add a computed column that basically gives you the reverse of ‘Farley’, index the computed column, then do your search on REVERSE(‘%arley’) – might have to have a play.</p>
<p>That said – isn’t this something that gets fixed to some degree by using full text search?</p>
<p>Cheers</p>
<p>Jez</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
