What Is a Database Transaction? Explained

What a transaction is

A database transaction is a group of operations that are treated as a single, indivisible unit: either all of them succeed, or none of them do. If any part fails, the whole transaction is undone, leaving the database as if nothing happened. This 'all or nothing' behavior is crucial for keeping data correct when a single logical action involves multiple steps. Transactions are a fundamental feature of reliable databases, protecting data from being left in a broken, half-finished state.

The classic example

The textbook example is a bank transfer. Moving money from one account to another involves two steps: subtract from the first account and add to the second. If the system crashed after the first step but before the second, money would simply vanish. A transaction prevents this: both steps are bundled together, so either the full transfer happens or neither part does. This guarantees the accounts always add up, no matter what goes wrong mid-process.

Commit and rollback

Transactions have two key outcomes. 'Commit' makes all the changes in the transaction permanent, once everything has succeeded. 'Rollback' undoes all the changes, returning the database to its state before the transaction began, used when something goes wrong. This pair of actions is what delivers the all-or-nothing guarantee: the database holds the changes tentatively until it can either commit them all or roll them all back cleanly.

The ACID properties

Reliable transactions are often described by four properties summarized as ACID. Atomicity means all-or-nothing. Consistency means a transaction leaves the database in a valid state. Isolation means concurrent transactions do not interfere with each other improperly. Durability means once committed, changes survive even a crash or power loss. Together, these ACID properties define what it means for a database to handle transactions reliably, and they are a hallmark of trustworthy database systems.

Handling many at once

Real databases often process many transactions at the same time, and they must not corrupt each other. The 'isolation' property ensures that simultaneous transactions behave as if they ran one after another, so one transaction cannot see another's half-finished work. Managing this concurrency correctly is one of the most challenging parts of building a database, but it is essential, which is why robust transaction support is such a valued feature in serious database systems.

Why it matters

Transactions are essential to keeping data correct and trustworthy, especially for anything involving money, inventory, or other critical records. Understanding them, and the ACID properties that define reliable transactions, clarifies how databases protect against errors, crashes, and conflicts. For anyone learning how important systems keep their data consistent, the database transaction is a core concept that underpins the reliability we take for granted.

Related on Skillo

See also: What is a relational database? Explained, What is SQL? Explained simply.

Sources

• Database transaction - Wikipedia

Published date reflects the original event date (2024-06-18). This article is original Skillo editorial written from the sources above; facts were verified in September 2026.