PRB: Full-Text Catalog May be Lost After Restoring Suspect Database using WITH REPLACE

• Microsoft SQL Server version 7.0

SYMPTOMS

When a user database that has full-text search catalogs is marked suspect and is then restored from a backup using the WITH REPLACE option, the full-text catalog may be lost. The full-text catalog will have to be rebuilt.

CAUSE

In response to the WITH REPLACE directive for RESTORE, if the database is marked as suspect, SQL Server drops the database before restoring over it. When the database is dropped it also deletes the full-text catalog for the dropped database. Full-text catalogs are not part of a database backup, so they can not be restored with the database.

WORKAROUND

Stop the Microsoft Search service (either from SQL Server Enterprise Manager or the Services application in Control Panel) prior to performing the database restore. After the database is restored successfully, restart the Microsoft Search service.

MORE INFORMATION

Since the database ID is used to track the catalog, the database should not be manually deleted and recreated for restore. This may result in a different database ID.

Loss of the full-text index catalog only happens when the database is actually damaged. Restoring a backup over a functioning database using WITH REPLACE will not delete the catalog.

Additional query words:

Keywords          : kbSQLServ700 
Version           : winnt:7.0
Platform          : winnt 
Issue type        : kbprb 

Last Reviewed: July 30, 1999