Using the Transaction Log File to Restore Commerce Server Databases to Moment of Failure

The SQL Server recovery process uses the transaction log file to ensure that your database is consistent. SQL Server examines the transaction log file from the last checkpoint to the point at which SQL Server failed or was shut down. A checkpoint is like a bookmark, marking the point at which all data changes are written to the database. If the transaction log file has committed transactions that have not yet been written to the database, SQL Server rolls these transactions forward, applying the changes to the database. If the transaction log file contains any uncommitted transactions, SQL Server rolls back these transactions. Uncommitted transactions are not written to the database.

Copyright © 2005 Microsoft Corporation.
All rights reserved.