sql server full text search: Hi!
I tried to use change tracking (with background or update index
options) and incremental index.

Change tracking is very fast!! Better then incremental function.
But my query are very slow now, time to make a query is doubled!
Can you help me to improve this behaviour?

Thanks!

With change tracking, you'll see realtime updates to the FT index
unlike incremental where it only gets updated when you start an
incremental population.
On the other hand, change tracking with background update index means
that your changelist will be monitored to trigger updates to the FT
index. Also, while performing an FT query, SQL will have to JOIN the
results of the FT query with the data table you're querying. Both of
these are I/O intensive operations. Is your FT catalog on a separate
disk from you DB data file, and your t-log file? This will reduce the
IO contention and give you better perf while indexing as well as
querying. You could also try setting the resource_usage higher.

There are a number of whitepapers on how you could achieve the optimum
performance given your system. Here's a few of them:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqlpro04/html/sp04f9.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql90/html/sql2005ftsearch.asp
http://msdn2.microsoft.com/en-us/library/ms142583.aspx

This should not be the case. Can you check to see if there is any locking,
also issue the following:

SELECT fulltextserviceproperty('resourceusage')

--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com



[quoted text, click to view]