I have a SQL 2000 full text catalog with Incremental population and Change
Tracking.
There is a replication job on the table , which replicates every 10 minutes.
Sometimes there is a delay from the time the data appears in the table , to
the point it appears in Full text catalog.
Is there a built - in mechanism where the indexing won't occur until CPU use
drops down to a certain level?

Signature
Jack Vamvas
___________________________________
Need an IT job? http://www.ITjobfeed.com
Jean-Pierre Riehl - 07 Aug 2007 21:49 GMT
Hi Jack,
Change Tracking involves a small latency. The more updates there is, the
longer latency is.
You cannot control how changes propagate in Full-Text index except using
Incremental population.

Signature
Jean-Pierre Riehl
http://blog.djeepy1.net
http://www.bewise.fr
>I have a SQL 2000 full text catalog with Incremental population and Change
>Tracking.
[quoted text clipped - 5 lines]
> Is there a built - in mechanism where the indexing won't occur until CPU
> use drops down to a certain level?
Hilary Cotter - 15 Aug 2007 10:44 GMT
No, but it pauses during a log backup and is throttled when the indexer
can't keep up with the gatherer.

Signature
relevantNoise - 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
>I have a SQL 2000 full text catalog with Incremental population and Change
>Tracking.
[quoted text clipped - 5 lines]
> Is there a built - in mechanism where the indexing won't occur until CPU
> use drops down to a certain level?