Why transactions are needed in SQL - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use transactions in databases?

Imagine you are transferring money between two bank accounts. Why is it important to use a transaction for this operation?

A To allow multiple users to change the same account balance at the same time without issues.

B To ensure both debit and credit happen together or not at all, preventing money loss.

C To speed up the transfer by skipping checks.

D To save the transfer details only after a day.

💡 Hint

Think about what happens if only one part of the transfer happens and the other does not.

Transactions make sure that all steps in a process happen completely or not at all. This avoids problems like losing money if only one step succeeds.

🧠 Conceptual

intermediate

What problem do transactions solve?

Which problem is solved by using transactions in a multi-user database?

A Preventing partial updates that leave data inconsistent.

B Making queries run faster by skipping locks.

C Allowing users to see uncommitted changes from others immediately.

D Automatically backing up data every minute.

💡 Hint

Think about what happens if a process stops halfway through.

Transactions prevent partial changes that could cause wrong or broken data when multiple users work at the same time.

❓ query_result

advanced

What is the output after a failed transaction?

Consider this SQL sequence:

BEGIN TRANSACTION;
UPDATE accounts SET balance = balance - 100 WHERE id = 1;
UPDATE accounts SET balance = balance + 100 WHERE id = 2;
ROLLBACK;

What is the balance change after this sequence?

A Account 1 decreased by 100, account 2 increased by 100.

B Account 1 balance decreased by 100, account 2 unchanged.

C Account 1 unchanged, account 2 increased by 100.

D No change in balances for both accounts.

💡 Hint

ROLLBACK cancels all changes in the transaction.

ROLLBACK undoes all changes made in the transaction, so balances remain as before.

❓ query_result

advanced

What happens without transactions in concurrent updates?

Two users update the same row at the same time without transactions:

User1: UPDATE inventory SET quantity = quantity - 1 WHERE product_id = 10;
User2: UPDATE inventory SET quantity = quantity - 1 WHERE product_id = 10;

What problem can occur?

A Quantity decreases correctly by 2.

B Both updates fail with an error.

C Both updates succeed but quantity only decreases by 1 instead of 2.

D Database automatically merges updates safely.

💡 Hint

Think about what happens if both read the same initial quantity before updating.

Without transactions and proper locking, both users might read the same quantity and overwrite each other's update, causing lost updates.

🧠 Conceptual

expert

Why is atomicity important in transactions?

Atomicity means a transaction is all-or-nothing. Why is this property crucial for database reliability?

A It prevents partial changes that could corrupt data if a failure occurs mid-operation.

B It speeds up query execution by skipping checks.

C It allows users to see intermediate results during a transaction.

D It automatically backs up data after each query.

💡 Hint

Consider what happens if a system crashes during a multi-step update.

Atomicity ensures that either all steps succeed or none do, so data never ends up in a broken or partial state.

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