To migrate the full-text indexes you should script them out and run them on
the destination server.
To migrate built catalogs review the following:
http://support.microsoft.com/kb/240867/en-us For sql 2005 do the following:
ALTER DATABASE database_name SET OFFLINE on both source and destination
stop msftesql on both
copy the catalog
alter the database files on the destination server to point to the catalog
location
ie, ALTER DATABASE database_name MODIFY FILE ( NAME = sys_fulltext,
FILENAME = 'c:\dump')
start msftesql
ALTER DATABASE database_name SET ONLINE
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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 [quoted text, click to view] <almurph@altavista.com> wrote in message
news:1153479842.270456.74550@75g2000cwc.googlegroups.com...
> Hi everyone,
>
>
> I noticed that when I did an export on a database (lets call it DB_a)
> to another one (lets call it DB_b) it did not copy over the full text
> index (FTI) that was on DB_a.
> Is there anyway I can get the FTI from DB_a to be copied over to DB_b
> without having to rebuild the FTI on DB_b??
>
> Would appreciate any comments/hints/user-experience that you may like
> to share.
>
> Thanking you,
> Al.
>