I have a customer that is complaining of poor performance when doing
searches against the FTS catalog during the day.
I believe what is happening is that the indexing process is taking place at
the same time as their searches.

select @@version
-------------------
Microsoft SQL Server  2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)

The data is derived from an OCR process on scanned forms.
The data is added to the table throughout the day.

The catalog index is on one column of one table.
I have Change Tracking, Update Index in Background enabled.

Question 1 - When Chg Trk, UIB is enabled, should I see the crawl start and
crawl end events enumerated in the event log?
I thought this operation went on continuously.
I have included an abridged listing from the event log for one day.
You can see that on average, 200-300 items are processed each iteration
during the day.
Is this typical of Change Tracking, UIB?

The following list displays the data for one day,

crawl start time
crawl end time, gatherer count, modified count

7:21 crawl start
8:43 crawl end     2031581     6

9:04 crawl start
10:29 crawl end     2033495     307

11:01 crawl start
12:22 crawl end     2034510     385

12:50 crawl start
14:14 crawl end     2035862     341

14:23 crawl start
15:49 crawl end     2036796     244

16:27 crawl start
17:48 crawl end     2038034     244

19:00 crawl start
20:21 crawl end     2038557     1

Since the crawl process runs for one to one and one-half hours each event, I
am guessing that this is what is affecting their performance.

Question 2 - Would it be better to turn off Change Tracking, UIB during the
day and start an incremental index in the evening?
I thought CT, UIB was designed to allow indexing to take place while normal
database operations are executing.