 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / Other Technologies / Full-Text Search / June 2007Incremental scans entire table rather than only changed rows
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 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.  SignatureLooking 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 > 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 [quoted text clipped - 10 lines] > also be issued 50 million times." > - Hilary Cotter > Change tracking is the best option for what you are looking for. 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. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.