Why transactions are needed in SQL - Quick Recap

Recall & Review

beginner

What is a database transaction?

A database transaction is a sequence of operations performed as a single logical unit of work. It ensures that either all operations succeed together or none do, keeping data consistent.

beginner

Why do we need transactions in databases?

Transactions help keep data accurate and reliable by making sure changes are complete and consistent, even if errors or crashes happen during the process.

intermediate

What does ACID stand for in transactions?

ACID stands for Atomicity, Consistency, Isolation, and Durability. These properties guarantee reliable processing of database transactions.

intermediate

Explain Atomicity in transactions.

Atomicity means a transaction is all or nothing. If any part fails, the whole transaction is rolled back so the database stays unchanged.

intermediate

How do transactions help when multiple users access the database?

Transactions isolate each user's work so they don't interfere with each other, preventing errors like lost updates or inconsistent data.

What happens if a transaction fails halfway through?

A Partial changes remain in the database

B All changes made by the transaction are undone

C The database crashes

D The transaction continues automatically

Transactions are atomic, so if any part fails, all changes are rolled back to keep data consistent.

Which property ensures that transactions do not affect each other?

A Durability

B Atomicity

C Consistency

D Isolation

Isolation keeps transactions separate so they don't interfere with each other's data.

Why is durability important in transactions?

A It makes sure changes are permanent even after a crash

B It allows partial updates

C It speeds up queries

D It prevents users from accessing data

Durability means once a transaction is committed, its changes are saved permanently.

Which of these is NOT a reason transactions are needed?

A To handle errors safely

B To keep data consistent

C To allow partial updates

D To manage multiple users

Transactions do not allow partial updates; they ensure all or nothing changes.

What does consistency mean in the context of transactions?

A Data stays valid before and after the transaction

B Transactions run faster

C Users can see partial changes

D Data is backed up automatically

Consistency means the database rules are followed and data remains valid after the transaction.

Explain why transactions are important for data integrity in databases.

Think about what happens if something goes wrong during multiple related changes.

Describe the ACID properties and how they relate to transactions.

Each letter in ACID stands for a key rule that makes transactions reliable.

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