restore to another server of db with FT catalogs

If we restore a backup copy of a production db having FT catalogs onto a
laptop running SQL Server Developer version, the restored db will contain
references to FT catalogs whose underlying system files are not yet present
on the laptop (because backup doesn't grab the FT system files). The index
rebuild takes only 20 minutes, so I'd prefer to recreate them rather than
move the FT system files. In that scenario, is it safe for the db on the
laptop to deactivate and drop the FT catalogs? Or can the missing system
files cause SQL Server to become unstable during the deactivation/drop
process? I'm thinking it shouldn't cause a problem, because if it did,
there'd be no way to drop a catalog whose system files had gotten corrupted.
But I lack the mental fortitude to experiment after the 7342 error consumed
most of my weekend, and am hoping you FTS gurus could handle this scenario
with your eyes closed and one arm tied behind your back. :-)
Thanks
Timo
consult this kb article for more information.
http://support.microsoft.com/default...b;en-us;240867
"Timo" <timo@.noneofyer.biz> wrote in message
news:eglQLxBGFHA.1188@.tk2msftngp13.phx.gbl...
> If we restore a backup copy of a production db having FT catalogs onto a
> laptop running SQL Server Developer version, the restored db will contain
> references to FT catalogs whose underlying system files are not yet
> present
> on the laptop (because backup doesn't grab the FT system files). The index
> rebuild takes only 20 minutes, so I'd prefer to recreate them rather than
> move the FT system files. In that scenario, is it safe for the db on the
> laptop to deactivate and drop the FT catalogs? Or can the missing system
> files cause SQL Server to become unstable during the deactivation/drop
> process? I'm thinking it shouldn't cause a problem, because if it did,
> there'd be no way to drop a catalog whose system files had gotten
> corrupted.
> But I lack the mental fortitude to experiment after the 7342 error
> consumed
> most of my weekend, and am hoping you FTS gurus could handle this scenario
> with your eyes closed and one arm tied behind your back. :-)
> Thanks
> Timo
>
|||Timo,
Yes, it is best to re-create the small FT Catalogs via normal procedures on
your laptop. However, successfully restoring a FT-enabled SQL Server 2000
database and then being able to re-create the lost FT Catalog depends upon
several factors - are the disk drives (drive letter & path) exactly the same
on the source server as the destination server? Are you restoring over an
existing database or are you restoring the database as a new database on the
laptop? The first factor will cause you problems (that can be overcome), the
second factor should work successfully. Overall, for SQL Server 2000 when
backing up FT-enabled databases, its best to disenable Full Text and then
backup the database...
You can also use the procedures in 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 to help you
as well understand these issues.
Hope that helps!
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Timo" <timo@.noneofyer.biz> wrote in message
news:eglQLxBGFHA.1188@.tk2msftngp13.phx.gbl...
> If we restore a backup copy of a production db having FT catalogs onto a
> laptop running SQL Server Developer version, the restored db will contain
> references to FT catalogs whose underlying system files are not yet
present
> on the laptop (because backup doesn't grab the FT system files). The index
> rebuild takes only 20 minutes, so I'd prefer to recreate them rather than
> move the FT system files. In that scenario, is it safe for the db on the
> laptop to deactivate and drop the FT catalogs? Or can the missing system
> files cause SQL Server to become unstable during the deactivation/drop
> process? I'm thinking it shouldn't cause a problem, because if it did,
> there'd be no way to drop a catalog whose system files had gotten
corrupted.
> But I lack the mental fortitude to experiment after the 7342 error
consumed
> most of my weekend, and am hoping you FTS gurus could handle this scenario
> with your eyes closed and one arm tied behind your back. :-)
> Thanks
> Timo
>
|||FYI, SQL 2K5 backups (as with sp_attach/detach_db) will contain FT indexes

"Timo" <timo@.noneofyer.biz> wrote in message
news:eglQLxBGFHA.1188@.tk2msftngp13.phx.gbl...
> If we restore a backup copy of a production db having FT catalogs onto a
> laptop running SQL Server Developer version, the restored db will contain
> references to FT catalogs whose underlying system files are not yet
present
> on the laptop (because backup doesn't grab the FT system files). The index
> rebuild takes only 20 minutes, so I'd prefer to recreate them rather than
> move the FT system files. In that scenario, is it safe for the db on the
> laptop to deactivate and drop the FT catalogs? Or can the missing system
> files cause SQL Server to become unstable during the deactivation/drop
> process? I'm thinking it shouldn't cause a problem, because if it did,
> there'd be no way to drop a catalog whose system files had gotten
corrupted.
> But I lack the mental fortitude to experiment after the 7342 error
consumed
> most of my weekend, and am hoping you FTS gurus could handle this scenario
> with your eyes closed and one arm tied behind your back. :-)
> Thanks
> Timo
>