Groups | Blog | Home
all groups > sql server full text search > june 2007 >

sql server full text search : Incremental scans entire table rather than only changed rows


Ian Boyd
6/3/2007 2:45:09 PM
The table being indexed has only one changed row, but when i do an
incremental population the table is being hit millions of times (millions of
rows). The table has a timestamp column.

How can i make incremental population only index rows that have changed?



(i already know the answer - incremental population is essentially the same
as full population. i'm just venting)

"If you have 50 million rows in your database, this procedure will be issued
50 million times.
On the other hand, if you use incremental population this statement will
also be issued 50 million times."
- Hilary Cotter
Hilary Cotter
6/6/2007 12:00:00 AM
This is by design. The crawl process must scan the entire table to determine
what has been removed from the table since the last incremental population.
Change tracking is the best option for what you are looking for.

--
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]

Ian Boyd
6/6/2007 4:55:23 PM
[quoted text, click to view]

i know, but this is on an SQL7 system.

It's sucky that i have to bog down the server for 4 hours, so that full-text
can update one row.


AddThis Social Bookmark Button