Microsoft KB Archive/62873

= INF: Backing Up and Recovering Databases =

Article ID: 62873

Article Last Modified on 11/14/2003

-

APPLIES TO


 * Microsoft SQL Server 4.21a Standard Edition
 * Microsoft SQL Server 6.0 Standard Edition
 * Microsoft SQL Server 6.5 Standard Edition

-



This article was previously published under Q62873



SUMMARY
The following information describes some considerations for backing up or restoring databases:
 * 1) When using log backups in combination with database backups, make sure you never truncate the log with either DUMP TRANSACTION WITH TRUNCATE_ONLY or TRUNCATE LOG ON CHECKPOINT. Any log backups following the truncation of the log are invalid and will generate an &quot;out of sequence&quot; error when restoring the transaction logs.

DUMP TRANSACTION has its own form of syslogs truncation. Therefore, in version 4.2x, it is important that each transaction dump is dumped onto a separate device, and that all are stored and restored in the same order.
 * 1) When only dumping databases, the transaction log must be truncated to keep it from becoming unnecessarily large because DUMP TRANSACTION does not truncate the log. In this instance, you should use TRUNCATE LOG ON CHECKPOINT.

Method 1 should be used for large databases so the whole database does not always need to be backed up. Method 2 is better suited for small databases.

Additional query words: Dumping and loading

Keywords: kbinfo kbother KB62873

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.