Post reply

Catalogs in creating back ups

  • June 10, 2010 at 4:17 am

    #219944

    Hi All,

    When I started taking backup from a database i got the errorTITLE: Microsoft SQL Server Management Studio

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

    Backup failed for Server 'BLRSRV15'. (Microsoft.SqlServer.Smo)

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Backup+Server&LinkId=20476

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

    ADDITIONAL INFORMATION:

    System.Data.SqlClient.SqlError: The backup of the file or filegroup "sysft_dbo.xxx"

    is not permitted because it is not online. BACKUP can be performed by using the FILEGROUP or FILE clauses to restrict

    the selection to include only online data. (Microsoft.SqlServer.Smo)

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&LinkId=20476

    from the net I understood that the full text search catalogs created in the Db is causing the problem.

    how to identify the catalogs in the database. and how to drop them

    Thanks,

    Regards

    Ami

  • June 10, 2010 at 9:40 pm

    #1179009

    Hi all,

    Got the remedy.

    Either you can do the following

    1. Locate the folder that contains the files for the problematic full-text catalog.

    2. Run the ALTER DATABASE statement. Specify in the statement the correct location for the full-text catalog.

    For more information about how to use the ALTER DATABASE statement in this scenario, visit the following Microsoft Developer Network (MSDN) Web site, and then search for the "Moving Full-Text Catalogs" topic:

    http://msdn2.microsoft.com/en-us/library/ms345483.aspx (http://msdn2.microsoft.com/en-us/library/ms345483.aspx)

    3. Rebuild the problematic full-text catalog in the database.

    4. Perform a full backup of the database in SQL Server 2005 again.

    or

    If you do not need the full-text catalog any longer, you can drop the problematic full-text catalog. Then, perform a full backup of the database in SQL Server 2005.

    to identify the catalogs in the DB use

    SELECT * FROM sys.fulltext_catalogs

    or system procedure

    EXEC sp_help_fulltext_catalogs

    Once you find the name of the catalog drop it using

    DROP FULLTEXT CATALOG 'catalogname'

    alternatively you can move the catalog to another location using alter database.

    Regards,

    Ami

Viewing 2 posts - 1 through 2 (of 2 total)

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