sql server full text search: there may be a merge in process when you see this pausing. Indexing may also
be paused due to low space, low battery or other reasons. Check the event
log for any messages from mssci or mssearch.

Can you also do a dir in your catalog location and post back the sizes of
the files you see there.

There was a problem when these files reached a certain size and you tried a
master merge.

[quoted text, click to view]
Hello,

When doing full or incremental population the gatherer process sometimes
just stops. The mssearch service still works, full text queries still
return results. I notice this by observing the performance monitor. The
population I setup proceeds normal for 1 hour, 2 hours or so, and then
suddenly it stops. The "waiting documents", "documents in progress", and
"started documents" performance counters stop moving. No error message in
the logs when this happens. Only way to get over this is to restart the
mssearch service and the population continues from where it stopped without
any problems

There may be from 350'000 to 850'000 rows in the tables involved in FT. The
data is text, some of the text columns are 2000 characters wide. Database
server is 4 CPU Dell box with 4G ram, busy production system with about 120
users connected on average at anytime. output of select @@version is :
Microsoft SQL Server 2000 - 8.00.818 (Intel X86) May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows
NT 5.0 (Build 2195: Service Pack 4)

Does anybody have any idea what could cause this and how to prevent it? Any
advice would be greatly appreciated.

Ray

Hello,

When doing full or incremental population the gatherer process sometimes =
just stops. The mssearch service still works, full text queries still =
return results. I notice this by observing the performance monitor. =
The population I setup proceeds normal for 1 hour, 2 hours or so, and =
then suddenly it stops. The "waiting documents", "documents in =
progress", and "started documents" performance counters stop moving. No =
error message in the logs when this happens. Only way to get over this =
is to restart the mssearch service and the population continues from =
where it stopped without any problems

There may be from 350'000 to 850'000 rows in the tables involved in FT. =
The data is text, some of the text columns are 2000 characters wide. =
Database server is 4 CPU Dell box with 4G ram, busy production system =
with about 120 users connected on average at anytime. output of select =
@@version is : Microsoft SQL Server 2000 - 8.00.818 (Intel X86) May =
31 2003 16:08:15 Copyright (c) 1988-2003 Microsoft Corporation =
Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4)=20

Does anybody have any idea what could cause this and how to prevent it? =
Any advice would be greatly appreciated.

Ray