Rollback (data management) in the context of Multiversion concurrency control

⭐ Core Definition: Rollback (data management)

In database technologies, a rollback is an operation which returns the database to some previous state. Rollbacks are important for database integrity, because they mean that the database can be restored to a clean copy even after erroneous operations are performed. They are crucial for recovering from database server crashes; by rolling back any transaction which was active at the time of the crash, the database is restored to a consistent state.

The rollback feature is usually implemented with a transaction log, but can also be implemented via multiversion concurrency control.

↓ Menu

Rollback (data management) in the context of Transaction log

In the field of databases in computer science, a transaction log (also transaction journal, database log, binary log or audit trail) is a history of actions executed by a database management system used to guarantee ACID properties over crashes or hardware failures. Physically, a log is a file listing changes to the database, stored in a stable storage format.

If, after a start, the database is found in an inconsistent state or not been shut down properly, the database management system reviews the database logs for uncommitted transactions and rolls back the changes made by these transactions. Additionally, all transactions that are already committed but whose changes were not yet materialized in the database are re-applied. Both are done to ensure atomicity and durability of transactions.

View the full Wikipedia page for Transaction log

↑ Return to Menu

Rollback (data management) in the context of Multiversion concurrency control

Rollback (data management) Study page number 1 of 1

Play TriviaQuestions Online!

Skip to study material about Rollback (data management) in the context of "Multiversion concurrency control"

⭐ Core Definition: Rollback (data management)

Rollback (data management) in the context of Transaction log