INF: Restoration of a Database from Transaction Dumps

 Last reviewed: April 25, 1997
Article ID: Q60054

The information in this article applies to: 

  - Microsoft SQL Server version 4.2 for OS/2

To restore a database that used DUMP TRANSACTION as the primary backup procedure, the last dump of the entire database (DUMP DATABASE) must be loaded (LOAD DATABASE), followed by the sequential loading (LOAD TRANSACTION) of the transaction dump(s) (DUMP TRANSACTION).

For example, if all of the following are true

  • The database was last dumped on Monday
  • The transactions were dumped Tuesday, Wednesday, Thursday, and Friday
  • The database crashed on Saturday, causing data corruption

the proper way to restore the database would be to first load the database dump from Monday, followed by the sequential loading of the transaction dumps from Tuesday, Wednesday, Thursday, and Friday. The database would then be restored to the state it was in as of the last transaction dump taken on Friday.

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.