ACID properties mental model in SQL

Introduction

ACID properties help keep data safe and correct when many people use a database at the same time.

When you want to make sure money transfers between bank accounts are accurate and safe.

When multiple users update the same data, like booking seats for a concert.

When you want to avoid losing data if the computer crashes during a save.

When you need to keep data consistent after many changes.

When you want to make sure partial changes don't happen if something goes wrong.

Syntax

SQL

-- ACID is a set of rules, not a query syntax
-- It stands for:
-- A: Atomicity
-- C: Consistency
-- I: Isolation
-- D: Durability

ACID is not a command but a set of principles databases follow.

These properties work together to keep data reliable and safe.

Examples

This means both updates happen together or not at all.

SQL

-- Atomicity example
BEGIN TRANSACTION;
UPDATE accounts SET balance = balance - 100 WHERE id = 1;
UPDATE accounts SET balance = balance + 100 WHERE id = 2;
COMMIT;

Database keeps data rules true after changes.

SQL

-- Consistency example
-- A rule: balance cannot be negative
UPDATE accounts SET balance = balance - 100 WHERE id = 1;
-- If balance < 0, rollback should happen (application or trigger logic required).

Changes don't mix up or interfere.

SQL

-- Isolation example
-- Two users update different accounts at the same time
-- Each sees their own changes only after commit.

Data is saved safely on disk.

SQL

-- Durability example
-- After COMMIT, changes stay even if power fails.

Sample Program

This simulates transferring 50 units from account 1 to account 2 safely.

SQL

BEGIN TRANSACTION;
UPDATE accounts SET balance = balance - 50 WHERE id = 1;
UPDATE accounts SET balance = balance + 50 WHERE id = 2;
COMMIT;

SELECT id, balance FROM accounts ORDER BY id;

Important Notes

Atomicity means all parts of a change happen or none do.

Consistency means data rules are always true.

Isolation means changes don't mix up when many users work together.

Durability means once saved, data won't be lost.

Summary

ACID keeps data safe and correct in databases.

It stands for Atomicity, Consistency, Isolation, and Durability.

These properties work together to handle many users and failures smoothly.

Practice

1. Which ACID property ensures that a transaction is completed fully or not at all, like finishing a whole recipe or not starting it?

easy

A. Isolation

B. Consistency

C. Atomicity

D. Durability

Solution

1. Step 1: Understand Atomicity meaning

   Atomicity means a transaction is all-or-nothing, like a recipe that must be fully done or not started.

2. Step 2: Compare with other properties

   Consistency means data rules are followed, Isolation means transactions don't interfere, Durability means changes are saved permanently.

3. Final Answer:

   Atomicity -> Option C

4. Quick Check:

   All or nothing = Atomicity [OK]

Hint: All or nothing means Atomicity [OK]

Common Mistakes:

• Confusing Consistency with Atomicity
• Thinking Isolation means all-or-nothing
• Mixing Durability with Atomicity

2. Which of the following SQL transaction commands is used to make all changes permanent, supporting the Durability property?

easy

A. ROLLBACK

B. COMMIT

C. SAVEPOINT

D. BEGIN TRANSACTION

Solution

1. Step 1: Identify command for saving changes

   COMMIT saves all changes permanently, ensuring Durability.

2. Step 2: Understand other commands

   ROLLBACK undoes changes, SAVEPOINT marks a point to rollback to, BEGIN TRANSACTION starts a transaction.

3. Final Answer:

   COMMIT -> Option B

4. Quick Check:

   Permanent save = COMMIT [OK]

Hint: COMMIT makes changes permanent [OK]

Common Mistakes:

• Choosing ROLLBACK to save changes
• Confusing SAVEPOINT with COMMIT
• Thinking BEGIN TRANSACTION saves data

3. Consider two transactions running at the same time: Transaction 1 adds 100 to an account balance, Transaction 2 subtracts 50. Which ACID property ensures the final balance is correct as if transactions ran one after another?

medium

A. Isolation

B. Consistency

C. Atomicity

D. Durability

Solution

1. Step 1: Understand concurrent transactions

   When two transactions run together, Isolation ensures they don't interfere and produce correct results.

2. Step 2: Differentiate from other properties

   Atomicity is about all-or-nothing, Consistency is about data rules, Durability is about saving changes permanently.

3. Final Answer:

   Isolation -> Option A

4. Quick Check:

   Transactions separated = Isolation [OK]

Hint: No interference means Isolation [OK]

Common Mistakes:

• Mixing Consistency with Isolation
• Thinking Atomicity handles concurrency
• Confusing Durability with Isolation

4. A developer notices that after a system crash, some committed transactions are lost. Which ACID property is likely violated, and what should be fixed?

medium

A. Atomicity; ensure transactions are all-or-nothing

B. Consistency; fix data validation rules

C. Isolation; improve transaction locking

D. Durability; improve data saving and recovery

Solution

1. Step 1: Identify property related to crash recovery

   Durability ensures committed transactions survive crashes and are saved permanently.

2. Step 2: Match problem to property

   Lost committed transactions after crash means Durability is violated and saving/recovery must be improved.

3. Final Answer:

   Durability; improve data saving and recovery -> Option D

4. Quick Check:

   Crash survival = Durability [OK]

Hint: Lost data after crash means Durability issue [OK]

Common Mistakes:

• Confusing Atomicity with crash recovery
• Thinking Isolation fixes lost data
• Mixing Consistency with durability problems

5. A bank system must ensure that transferring money from one account to another never leaves the database in an incorrect state, even if the system crashes or many users act at once. Which combination of ACID properties best guarantees this?

hard

A. Atomicity, Consistency, and Durability

B. Consistency and Isolation

C. Isolation and Durability

D. Atomicity and Durability

Solution

1. Step 1: Identify properties needed for correctness and crash safety

   Atomicity ensures full transfer or none, Consistency keeps data valid, Durability saves changes permanently.

2. Step 2: Understand why Isolation alone is not enough

   Isolation prevents interference but does not guarantee correctness or crash safety alone.

3. Step 3: Combine properties for full guarantee

   Atomicity + Consistency + Durability together ensure safe, correct, and permanent transfers.

4. Final Answer:

   Atomicity, Consistency, and Durability -> Option A

5. Quick Check:

   Safe + correct + permanent = Atomicity + Consistency + Durability [OK]

Hint: All but Isolation ensure correctness and crash safety [OK]

Common Mistakes:

• Ignoring Consistency in correctness
• Thinking Isolation alone is enough
• Missing Durability for crash safety