Why transactions are needed in SQL - See It in Action

Understanding Why Transactions Are Needed in Databases

📖 Scenario: You are managing a small online bookstore database. Multiple users can buy books at the same time. You want to make sure that the stock count updates correctly even if many purchases happen simultaneously.

🎯 Goal: Build a simple transaction example that shows how to safely update the stock of a book when a purchase happens, preventing errors like selling more books than available.

📋 What You'll Learn

Create a table called books with columns id, title, and stock

Insert one book with id = 1, title = 'Learn SQL', and stock = 10

Start a transaction to buy 3 copies of the book with id = 1

Update the stock by subtracting 3 only if enough stock is available

Commit the transaction to save changes

💡 Why This Matters

🌍 Real World

Online stores and inventory systems use transactions to keep stock counts accurate and avoid selling items that are out of stock.

💼 Career

Understanding transactions is essential for database administrators and developers to ensure data integrity and consistency in multi-user environments.

1

Create the books table and insert initial data

Write SQL code to create a table called books with columns id (integer primary key), title (text), and stock (integer). Then insert one row with id = 1, title = 'Learn SQL', and stock = 10.

SQL

-- Your code here to create the table and insert the book

Hint

Use CREATE TABLE to make the table and INSERT INTO to add the book.

2

Start a transaction to buy books

Write SQL code to start a transaction using BEGIN TRANSACTION;.

SQL

CREATE TABLE books (
  id INTEGER PRIMARY KEY,
  title TEXT,
  stock INTEGER
);

INSERT INTO books (id, title, stock) VALUES (1, 'Learn SQL', 10);

-- Start the transaction here
-- Your code here

Hint

Use BEGIN TRANSACTION; to start the transaction.

3

Update stock only if enough books are available

Write an UPDATE statement to reduce the stock by 3 for the book with id = 1, but only if the current stock is at least 3. Use a WHERE clause to check this condition.

SQL

CREATE TABLE books (
  id INTEGER PRIMARY KEY,
  title TEXT,
  stock INTEGER
);

INSERT INTO books (id, title, stock) VALUES (1, 'Learn SQL', 10);

BEGIN TRANSACTION;

-- Update stock if enough copies are available
-- Your code here

Hint

Use UPDATE with a WHERE clause to check stock before subtracting.

4

Commit the transaction to save changes

Write SQL code to commit the transaction using COMMIT;.

SQL

CREATE TABLE books (
  id INTEGER PRIMARY KEY,
  title TEXT,
  stock INTEGER
);

INSERT INTO books (id, title, stock) VALUES (1, 'Learn SQL', 10);

BEGIN TRANSACTION;

UPDATE books SET stock = stock - 3 WHERE id = 1 AND stock >= 3;

-- Commit the transaction
-- Your code here

Hint

Use COMMIT; to save the changes made in the transaction.

Practice

1. Why do we need transactions in a database?
BEGIN TRANSACTION; UPDATE accounts SET balance = balance - 100 WHERE id = 1; UPDATE accounts SET balance = balance + 100 WHERE id = 2; COMMIT;

easy

A. To make sure all steps succeed or none do, keeping data correct

B. To speed up the database queries

C. To allow multiple users to read data at the same time

D. To permanently delete data from the database

Solution

1. Step 1: Understand the purpose of transactions

   Transactions group multiple steps so they all succeed or all fail together, preventing partial updates.

2. Step 2: Analyze the example code

   The example moves money between accounts; if one update fails, the transaction rolls back to keep balances correct.

3. Final Answer:

   To make sure all steps succeed or none do, keeping data correct -> Option A

4. Quick Check:

   Transactions ensure data integrity = A [OK]

Hint: Transactions keep data safe by grouping steps [OK]

Common Mistakes:

• Thinking transactions speed up queries
• Confusing transactions with data deletion
• Believing transactions only allow multiple readers

2. Which of the following is the correct way to start a transaction in SQL?

easy

A. OPEN TRANSACTION;

B. CREATE TRANSACTION;

C. START TRANSACTION;

D. BEGIN TRANSACTION;

Solution

1. Step 1: Recall SQL syntax for transactions

   The standard way to start a transaction is using START TRANSACTION; or BEGIN TRANSACTION;.

2. Step 2: Check each option

   START TRANSACTION; is the most widely supported and standard syntax. CREATE TRANSACTION and OPEN TRANSACTION are invalid. BEGIN TRANSACTION is valid in some systems but START TRANSACTION is more standard.

3. Final Answer:

   START TRANSACTION; -> Option C

4. Quick Check:

   Start transaction command = START TRANSACTION [OK]

Hint: Use START TRANSACTION to start safely [OK]

Common Mistakes:

• Using CREATE TRANSACTION which is invalid
• Confusing START TRANSACTION with BEGIN TRANSACTION
• Trying OPEN TRANSACTION which doesn't exist

3. Consider this SQL transaction:

BEGIN TRANSACTION;
UPDATE inventory SET quantity = quantity - 5 WHERE product_id = 10;
UPDATE sales SET total = total + 5 WHERE sale_id = 3;
ROLLBACK;

What will be the final effect on the database?

medium

A. Both updates will be saved permanently

B. No changes will be saved to the database

C. Only the first update will be saved

D. Only the second update will be saved

Solution

1. Step 1: Understand the effect of ROLLBACK

   ROLLBACK cancels all changes made in the current transaction, undoing updates.

2. Step 2: Analyze the transaction steps

   Two updates happen, but ROLLBACK is called before COMMIT, so none of the changes are saved.

3. Final Answer:

   No changes will be saved to the database -> Option B

4. Quick Check:

   ROLLBACK cancels changes = C [OK]

Hint: ROLLBACK undoes all changes in a transaction [OK]

Common Mistakes:

• Assuming updates save without COMMIT
• Thinking partial updates remain after ROLLBACK
• Confusing ROLLBACK with COMMIT

4. This SQL code tries to transfer money but has an error:

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

What is the error and how to fix it?

medium

A. Missing semicolon after COMMIT; add ; to fix

B. Wrong order of updates; swap the two UPDATE statements

C. Should use ROLLBACK instead of COMMIT

D. BEGIN TRANSACTION is invalid syntax; use START TRANSACTION

Solution

1. Step 1: Check SQL statement syntax

   Each SQL statement must end with a semicolon. The COMMIT statement is missing a semicolon.

2. Step 2: Fix the syntax error

   Add a semicolon after COMMIT to complete the transaction properly.

3. Final Answer:

   Missing semicolon after COMMIT; add ; to fix -> Option A

4. Quick Check:

   SQL statements end with ; = B [OK]

Hint: End SQL statements with semicolon ; [OK]

Common Mistakes:

• Ignoring missing semicolon causing syntax error
• Thinking ROLLBACK replaces COMMIT here
• Believing transaction start syntax is wrong

5. You want to transfer $200 from account A to account B safely. Which transaction sequence ensures no money is lost if the second update fails?

1. BEGIN TRANSACTION;
2. UPDATE accounts SET balance = balance - 200 WHERE id = A;
3. UPDATE accounts SET balance = balance + 200 WHERE id = B;
4. COMMIT;

What should you add to handle failure properly?

hard

A. Use DELETE instead of UPDATE for account balances

B. Remove BEGIN TRANSACTION to speed up updates

C. Add COMMIT before step 3 to save first update early

D. Add ROLLBACK after step 3 if the second update fails

Solution

1. Step 1: Understand transaction failure handling

   If the second update fails, the transaction should be undone to avoid losing money.

2. Step 2: Use ROLLBACK to undo partial changes

   Adding ROLLBACK after detecting failure cancels all changes, keeping data consistent.

3. Step 3: Avoid premature COMMIT or removing transaction

   Committing early or removing transaction risks partial updates and data loss.

4. Final Answer:

   Add ROLLBACK after step 3 if the second update fails -> Option D

5. Quick Check:

   Use ROLLBACK on failure = A [OK]

Hint: Rollback if any step fails to keep data safe [OK]

Common Mistakes:

• Committing before all steps succeed
• Removing transaction causing partial updates
• Using DELETE instead of UPDATE for balances