<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Getting Started with SQL Server 2005 Full Text Searching: Part 2 – The Indexes</title>
	<atom:link href="http://arcanecode.com/2007/06/27/getting-started-with-sql-server-2005-full-text-searching-part-2-%e2%80%93-the-indexes/feed/" rel="self" type="application/rss+xml" />
	<link>http://arcanecode.com/2007/06/27/getting-started-with-sql-server-2005-full-text-searching-part-2-%e2%80%93-the-indexes/</link>
	<description>Making Microsoft .Net Development Magical</description>
	<lastBuildDate>Tue, 07 Feb 2012 16:57:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: J.T. Wentworth</title>
		<link>http://arcanecode.com/2007/06/27/getting-started-with-sql-server-2005-full-text-searching-part-2-%e2%80%93-the-indexes/#comment-27514</link>
		<dc:creator><![CDATA[J.T. Wentworth]]></dc:creator>
		<pubDate>Tue, 23 Feb 2010 01:41:37 +0000</pubDate>
		<guid isPermaLink="false">http://arcanecode.wordpress.com/2007/06/27/getting-started-with-sql-server-2005-full-text-searching-part-2-%e2%80%93-the-indexes/#comment-27514</guid>
		<description><![CDATA[Thank you for the great information.  I look forward to seeing more articles and what else you have to offer!]]></description>
		<content:encoded><![CDATA[<p>Thank you for the great information.  I look forward to seeing more articles and what else you have to offer!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Full Text Searching a FILESTREAM VARBINARY (MAX) Column &#171; Arcane Code</title>
		<link>http://arcanecode.com/2007/06/27/getting-started-with-sql-server-2005-full-text-searching-part-2-%e2%80%93-the-indexes/#comment-26757</link>
		<dc:creator><![CDATA[Full Text Searching a FILESTREAM VARBINARY (MAX) Column &#171; Arcane Code]]></dc:creator>
		<pubDate>Thu, 28 May 2009 06:06:36 +0000</pubDate>
		<guid isPermaLink="false">http://arcanecode.wordpress.com/2007/06/27/getting-started-with-sql-server-2005-full-text-searching-part-2-%e2%80%93-the-indexes/#comment-26757</guid>
		<description><![CDATA[[...] The second parameter indexes the VARBINARY(MAX) “Document” column itself, but notice the TYPE COLUMN after the column name. In order to Full Text Index a VARBINARY(MAX) column you must also have a column with the file extension in it. You then pass in the name of column after the TYPE COLUMN. In this example, the document extension is stored in the “DocumentExtension” column. Since the document extension can be stored in a column with any name, we let the Full Text engine know which column by passing it in after the TYPE COLUMN keyword. The remainder of the command is like other examples I’ve shown in the past. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] The second parameter indexes the VARBINARY(MAX) “Document” column itself, but notice the TYPE COLUMN after the column name. In order to Full Text Index a VARBINARY(MAX) column you must also have a column with the file extension in it. You then pass in the name of column after the TYPE COLUMN. In this example, the document extension is stored in the “DocumentExtension” column. Since the document extension can be stored in a column with any name, we let the Full Text engine know which column by passing it in after the TYPE COLUMN keyword. The remainder of the command is like other examples I’ve shown in the past. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SQL Server Full Text Searching at the Atlanta Code Camp &#171; Arcane Code</title>
		<link>http://arcanecode.com/2007/06/27/getting-started-with-sql-server-2005-full-text-searching-part-2-%e2%80%93-the-indexes/#comment-26531</link>
		<dc:creator><![CDATA[SQL Server Full Text Searching at the Atlanta Code Camp &#171; Arcane Code]]></dc:creator>
		<pubDate>Mon, 16 Mar 2009 04:41:00 +0000</pubDate>
		<guid isPermaLink="false">http://arcanecode.wordpress.com/2007/06/27/getting-started-with-sql-server-2005-full-text-searching-part-2-%e2%80%93-the-indexes/#comment-26531</guid>
		<description><![CDATA[[...] 0 - Getting the Bits to do Full Text Searching in SQL Server 2005 Lesson 1 - The Catalog Lesson 2 - The Indexes Lesson 3 - Using SQL Lesson 4 - Valid Data Types Lesson 5 - Advanced [...]]]></description>
		<content:encoded><![CDATA[<p>[...] 0 &#8211; Getting the Bits to do Full Text Searching in SQL Server 2005 Lesson 1 &#8211; The Catalog Lesson 2 &#8211; The Indexes Lesson 3 &#8211; Using SQL Lesson 4 &#8211; Valid Data Types Lesson 5 &#8211; Advanced [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: intelligentmonster</title>
		<link>http://arcanecode.com/2007/06/27/getting-started-with-sql-server-2005-full-text-searching-part-2-%e2%80%93-the-indexes/#comment-25882</link>
		<dc:creator><![CDATA[intelligentmonster]]></dc:creator>
		<pubDate>Wed, 10 Sep 2008 10:26:11 +0000</pubDate>
		<guid isPermaLink="false">http://arcanecode.wordpress.com/2007/06/27/getting-started-with-sql-server-2005-full-text-searching-part-2-%e2%80%93-the-indexes/#comment-25882</guid>
		<description><![CDATA[Hi, great post.
As for change_tracking: I defined some indexes with auto change_tracking (I need to track 20-25 tables) and discovered, that it took 100% CPU, and stopped indexing tables at all. I read somewhere afterward, that each tracking trigger fired catalog population. Since incremental population takes some time to finish, for frequently updated tables trigger is fired more frequently, so population is never going to be completed.
When I stopped change tracking and defiled incremental population to run on hourly basis, FTS returned to normal working.]]></description>
		<content:encoded><![CDATA[<p>Hi, great post.<br />
As for change_tracking: I defined some indexes with auto change_tracking (I need to track 20-25 tables) and discovered, that it took 100% CPU, and stopped indexing tables at all. I read somewhere afterward, that each tracking trigger fired catalog population. Since incremental population takes some time to finish, for frequently updated tables trigger is fired more frequently, so population is never going to be completed.<br />
When I stopped change tracking and defiled incremental population to run on hourly basis, FTS returned to normal working.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

