Hi, we're having a problem with a full-text index not picking up new
rows that have been added since a recent DB server upgrade.
We migrated our database from SQL Server 2000 to 2005 last week (and
to a new machine as well). I copied over the tables, recreated the
index, and everything was working fine.
This week I copied over new data (overwriting the existing data) with
new rows. I have re-created the index, restarted the MS Search
service, and populated and repopulated the catalog, but the new 25
rows that were added since the original migration are not showing up
although they are clearly in the table and come up in regular
selects. Change tracking is set to "automatic" for this index.
Please help me figure this out.
Thanks,
Bernadette
Hilary Cotter - 27 Sep 2007 03:17 GMT
Can you check the gatherer logs. It is possible that SQL FTS is having a
problem indexing these rows.

Signature
RelevantNoise.com - dedicated to mining blogs for business intelligence.
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
> Hi, we're having a problem with a full-text index not picking up new
> rows that have been added since a recent DB server upgrade.
[quoted text clipped - 13 lines]
> Thanks,
> Bernadette