FIX: Unable to Restore to a Point in Time in First Transaction Log Backup (260182)
The information in this article applies to:
- Microsoft SQL Server 2000 (all editions)
- Microsoft SQL Server 7.0
This article was previously published under Q260182 BUG #: 235804 (SHILOH_BUGS) BUG #: 57677 (SQLBUG_70)
SYMPTOMS You cannot restore to a point in time within the first
transaction log backup for a database when you use SQL Server Enterprise
Manager to perform the RESTORE operation. In SQL Server 7.0, despite
the value entered by the user, the GUI always defaults to the time at the end
of the first transaction log. In SQL Server 2000, the following
error message occurs if you enter a point in time within the first transaction
log: The time specified is less than the minimum point
in time allowed. Time corrected. After the user clicks OK to close the message box, you find that the end time of the
transaction log has replaced the time entered earlier. The
subsequent execution of the RESTORE command restores the database to the end of
first transaction log backup. RESOLUTIONSQL Server 2000To resolve this problem, obtain the latest
service pack for Microsoft SQL Server 2000. For additional information, click
the following article number to view the article in the Microsoft Knowledge
Base: 290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
SQL Server 7.0To resolve this problem, obtain the latest
service pack for Microsoft SQL Server 7.0. For additional information, click
the following article number to view the article in the Microsoft Knowledge
Base: 301511 INF: How to Obtain the Latest SQL Server 7.0 Service Pack
WORKAROUND Use the RESTORE LOG statement in SQL Server Query Analyzer
with the STOPAT parameter to restore the database to a point in time within the
first transaction log backup. STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
SQL Server 2000
This problem was first corrected in Microsoft SQL Server 2000 Service Pack
2.
SQL Server 7.0
This problem was first corrected in Microsoft SQL Server 7.0 Service Pack
4.
Modification Type: | Major | Last Reviewed: | 10/31/2003 |
---|
Keywords: | kbBackup kbBug kbfix KB260182 |
---|
|