That helps a little. What I'm looking for is this: if the catalog is paused,
what is not running in the catalog? Are the indexes still useable, etc.
Can you point me to some documentation on the meaning of all the catalog
statuses? I've looked at all the microsoft documentation I can find and some
we searches, but no luck.
Thanks.
> It could mean you are on battery power, low disk space, low memory. Use the
> gatherer logs to interpret further.
[quoted text clipped - 3 lines]
> >
> > Thanks.
You can still query when the indexing process is paused; you just won't be
able to index new content.
Regarding the status - does this help?
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_fa-f
z_7x15.asp

Signature
Hilary Cotter
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
> That helps a little. What I'm looking for is this: if the catalog is paused,
> what is not running in the catalog? Are the indexes still useable, etc.
[quoted text clipped - 12 lines]
> > >
> > > Thanks.
muley - 20 Jul 2005 15:50 GMT
The link you gave me below is the only info I can find on the the statuses,
and it only lists what they are, not their meaning and what special
conditions are in effect when the catalog is in these states (like indexing
stopped, indexes not available, etc.).
> You can still query when the indexing process is paused; you just won't be
> able to index new content.
[quoted text clipped - 22 lines]
> > > >
> > > > Thanks.
muley - 20 Jul 2005 16:08 GMT
I have change-tracking background index update running. When I insert new
records into the table, the catalog status changes from "change tracking" to
"paused", back and forth several times, while the ~20k rows are being
inserted.
Are all the inserted records being indexed?
Thanks for the help.
> You can still query when the indexing process is paused; you just won't be
> able to index new content.
[quoted text clipped - 22 lines]
> > > >
> > > > Thanks.