FIX: Restore Filegroup Allowed After Truncating the Transaction Log

Article translations Article translations
Article ID: 248798 - View products that this article applies to.
This article was previously published under Q248798
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 55817 (SQLBUG_70)
Expand all | Collapse all

Symptoms

Restoring a filegroup backup after truncating the transaction log may leave the database in a logically inconsistent state.

After removing the active portion of the transaction log, such as using BACKUP LOG WITH TRUNCATE_ONLY, a RESTORE operation using the FILEGROUP option may be allowed under certain conditions.

The problem occurs if you perform the following steps:
  1. Your attempt to restore a filegroup backup fails with this error:
    Server: Msg 3159, Level 16, State 1, Line 2
    The tail of the log for database '%ls' has not been backed up. Back up the log and rerun the RESTORE statement specifying the FILE clause.
    Server: Msg 3013, Level 16, State 1, Line 2
    Backup or restore operation terminating abnormally.
  2. You then issue a BACKUP LOG WITH TRUNCATE_ONLY.
  3. You may now successfully restore the filegroup backup.

Status

Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.

Properties

Article ID: 248798 - Last Review: October 26, 2013 - Revision: 3.0
Applies to
  • Microsoft SQL Server 7.0 Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbfix KB248798

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com