Restoring DB with fulltext index to another server: index recreation steps?

When a database with fulltext indexes is restored to a different
server, what are the appropriate steps to take, and in what order,
to recreate the indexes on the new machine if it has a different
directory structure than the original server? Should the indexes
be removed and then recreated? Any problem removing the index if
the native file-system files cannot be located? The native file-
system index files are not brought over to the new machine as part
of the backup/restore process, is that right?
Thanks
TR
TR,
The best source of info on this is the KB article 240867 (Q240867) "INF: How
to Move, Copy, and Backup Full-Text Catalog Folders and Files" at
http://support.microsoft.com/default...b;EN-US;240867 This KB
article should answer most of your questions. However, in regards to the
following questions:
1. Any problem removing the index if the native file-system files cannot be
located?
A. It would be best to drop the FT Catalog prior to backing up the database
in this case.
2. The native file-system index files are not brought over to the new
machine as part of the backup/restore process, is that right?
A. That is correct. However, this will change in SQL Server 2005 (Yukon) as
the SQL Server backup & restore processes will be altered to include the FT
Catalog folder and files in the SQL Server 2005 database backup file.
Regards,
John
"TR" <TR@.anonymous.biz> wrote in message
news:MPG.1b2ba884d2593bac9896f7@.msnews.microsoft.c om...
> When a database with fulltext indexes is restored to a different
> server, what are the appropriate steps to take, and in what order,
> to recreate the indexes on the new machine if it has a different
> directory structure than the original server? Should the indexes
> be removed and then recreated? Any problem removing the index if
> the native file-system files cannot be located? The native file-
> system index files are not brought over to the new machine as part
> of the backup/restore process, is that right?
> Thanks
> TR