INF: Backing Up and Recovering Databases

 Last reviewed: April 25, 1997
Article ID: Q62873

The information in this article applies to: 

  - Microsoft SQL Server version 4.2 for OS/2

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 "out of sequence" error when restoring the transaction logs.

    DUMP TRANSACTION has its own form of syslogs truncation. Therefore, it is important that each transaction dump is dumped onto a separate device, and that all are stored and restored in the same order.

  2. 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 : kbother SSrvServer
Version : 4.2
Platform : OS/2
Issue type : kbtshoot

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 25, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.