Sign in
 
HomeLibraryLearnDownloadsTroubleshootingCommunityForums
SQL Server Developer Center >
> 
> 
Missing table after migration

Unanswered Missing table after migration

  • Monday, March 04, 2013 9:03 PM
     
     
    Sign In to Vote
    0

    Hi all,

      I am not sure this question is in the correct forum and if it is not please let me know where it should go.  We have moved our databases to another disk and when doing so also did some disk cleanup.  It appears that we may have deleted a file or folder that we should not have and this particular file/folder may not have been included in our backups.  The database seems to be working just fine however we get the following error when backing up...

    "Executing the query "BACKUP DATABASE [db_name]..." failed with the following error: "The backup of the file or filegroup "sysft_ftTblHelp_app" 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.
    BACKUP DATABASE is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly."

      I've searched through our backups to try and find this file/filegroup/etc however I am unable to locate where it may be.  Is there a way of figuring out what or where this file/filegroup is supposed to be located?  I've done a windows search and thus far have come up with nothing. 

      Thanks in advance for any help anyone might offer.


    • Edited by xGumbyx Monday, March 04, 2013 9:08 PM
    •  
     

All Replies

  • Monday, March 04, 2013 9:42 PM
    Moderator
     
     
    Sign In to Vote
    0

    Hello,

    Please read the workaround posted on the following thread:

    http://social.technet.microsoft.com/Forums/en-NZ/sqldisasterrecovery/thread/a3c5745f-6c3e-4bda-b80c-44ce9d7727a2

    "To work around this issue, please follow these steps:

        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.

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

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

    Notes:

        1. If you have not enabled the database for full-text indexing, you must enable this option first before you can perform a full backup of the database in SQL Server 2005.

        2. 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."


    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com