Hi,

[Fari Fazeli]

I am new with SQL Server 2005. I have found out that when rebuilding a catalog it also does a mass merge. It used to do this step at midnight in prior version. So I decided to break up the rebuilding by first droping and then creating the catalog:
---------------------------------------------------
1) exec sp_fulltext_catalog catalog_abc123, drop
2) exec sp_fulltext_catalog catalog_abc123, create
3) ALTER FULLTEXT CATALOG catalog_abc123
REBUILD WITH ACCENT_SENSITIVITY=ON
4) At midnight run:
ALTER FULLTEXT CATALOG catalog_abc123
REORGANIZE
---------------------------------------------------

But I got an error in setp #1 since the table for this catalog has an index. I have just finished populating the table. What's the best way to solve this problem?
Thanks,

Fari

[rmiao]

Why rebuild catalog? Can you just populate it instead?

[Fari Fazeli]

Thanks for the reply.
First, the table associated with this catalog gets overwritten each time (truncated and repopulated). So that's the reason and the fact that MASS MERGE under 2005 takes too long.
Given the above condition, don't I need to rebuild the catalog?

[rmiao]

But rebuild and reorganize do something.