Post reply

SQL Server 2005 - Repopulate Full Text Catalog After Migration

  • September 25, 2007 at 10:07 am

    #178074

    Posted - 09/25/2007 : 11:12:47

    --------------------------------------------------------------------------------

    I have Restored database from SQL server 2000 to SQL server 2005 and found that Full Text catalogs are not Populated.

    I tried using, exec sp_fulltext_catalog 'CatalogName', 'start_full' and it showed the message

    "Warning: Request to start a full-text index population on table or indexed view 'dbo.Corpora' is ignored because a population is currently active for this table or indexed view."

    Please let me know on "How to Repopulate all the Full text catalogs"

    Thanks.

  • September 25, 2007 at 10:33 am

    #736091

    You have to check the status of the full text catalog.

    Start with this one:

    select * from sys.master_files where type = 4

    also check out sys.fulltext_catalogs

  • September 25, 2007 at 11:52 am

    #736113

    am i wrong? i thought full text catalogs were not part of the database, but a separate file stored on the server, so you needed to back those up separetely, or recreate the full text after a restoration on a different server/different database

    linky after editing:

    http://support.microsoft.com/kb/240867

    SUMMARY

    Full-text catalogs and indexes are not stored in a SQL Server database. Full-text catalogs and indexes are stored in separate files that the Microsoft Search service manages. The full-text catalog files are not recovered during a Microsoft SQL Server recovery. Additionally, you cannot use the Transact SQL statements BACKUP and RESTORE to back up and to restore full-text catalog files. After recovery or restore operations, you must separately resynchronize the full-text catalogs. Only the Microsoft Windows NT system administrator and the Microsoft Search service can access the full-text catalog files.

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • September 25, 2007 at 12:14 pm

    #736117

    In SQL Server 2000 full text catalogs are indeed not backed up. However, information about the file location, tables and indexes remain in the database.

    With SQL Server 2005, full-text catalogs have become part of the standard backup/restore process.

  • September 25, 2007 at 12:18 pm

    #736120

    thank you Pam!

    I didn't know they did that in 2005. much easier to restore I assume, since it's part of the backup.

    In the original posters case, since the backup came from a 2000 backup, he'll need to rebuild no matter what, adn backup after they are rebuilt, right?

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • September 25, 2007 at 12:24 pm

    #736123

    Yup. But verification of status / file location / etc. is the first step.

    Regarding the backup / restore note that there is also a command to backup and/or restore the full text catalog only.

    BACKUP DATABASE database_name

    FILE = 'sysft_fulltext_cat'

    TO backup_device

  • September 26, 2007 at 1:18 am

    #736262

    Thanks very much, i was able to populate Full Text Catalogs now. 🙂

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply