How long to rebuild full-text catalog?

I started a rebuild of the full-text catalog on a 1 GB database an hour and a
half ago and it is still running. Is this normal. I've never done it before.
What's making me worry is there is very little CPU activity on the server so
I cant tell if its actually doing anything or if its hanging.
I also tried on a test version of the database which is on a workstation and
thats been running all day. I thought maybe just because its a 1ghz proc with
512MB ram. The CPU on the test box kicked in an hour ago with a process
called SQLWb.exe taking up all the processor. Ist that normal?I ran the following query:
select * from sys.master_files where database_id = 7 (7 is the id of the db
in question)
And the state says offline. Is that because I'm running the rebuild or
should that be fixed?
"Matt M" wrote:
> I started a rebuild of the full-text catalog on a 1 GB database an hour and a
> half ago and it is still running. Is this normal. I've never done it before.
> What's making me worry is there is very little CPU activity on the server so
> I cant tell if its actually doing anything or if its hanging.
> I also tried on a test version of the database which is on a workstation and
> thats been running all day. I thought maybe just because its a 1ghz proc with
> 512MB ram. The CPU on the test box kicked in an hour ago with a process
> called SQLWb.exe taking up all the processor. Ist that normal?|||I looked further into this and ran a query (cant remember what it was off the
top of my head) to find out the file location of the full text catalog and
when I went to the path it gave me, there was no file for it there. I'm
assuming this might be my problem.
A forum post recommended to just drop or delete the catalog but if I try
that I get an error:
TITLE: Microsoft SQL Server Management Studio
--
Drop failed for FullTextCatalog 'ftcat_documentindex'.
(Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Drop+FullTextCatalog&LinkId=20476
--
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
--
Full-Text Search is not enabled for the current database. Use
sp_fulltext_database to enable full-text search for the database. The
functionality to disable and enable full-text search for a database is
deprecated. Please change your application. (Microsoft SQL Server, Error:
7616)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=7616&LinkId=20476
--
BUTTONS:
OK
--
"Matt M" wrote:
> I ran the following query:
> select * from sys.master_files where database_id = 7 (7 is the id of the db
> in question)
> And the state says offline. Is that because I'm running the rebuild or
> should that be fixed?
>
> "Matt M" wrote:
> > I started a rebuild of the full-text catalog on a 1 GB database an hour and a
> > half ago and it is still running. Is this normal. I've never done it before.
> > What's making me worry is there is very little CPU activity on the server so
> > I cant tell if its actually doing anything or if its hanging.
> >
> > I also tried on a test version of the database which is on a workstation and
> > thats been running all day. I thought maybe just because its a 1ghz proc with
> > 512MB ram. The CPU on the test box kicked in an hour ago with a process
> > called SQLWb.exe taking up all the processor. Ist that normal?