[Solved] Why does a ROLLBACK command not undo changes after a COMMIT in a transaction? — Ans: Because COMMIT permanently saves changes, ending the transaction | SQL

SQL - Transactions and Data Integrity

Why does a ROLLBACK command not undo changes after a COMMIT in a transaction?

ABecause ROLLBACK only works before BEGIN TRANSACTION

BBecause ROLLBACK requires a SAVEPOINT to work

CBecause COMMIT permanently saves changes, ending the transaction

DBecause COMMIT delays saving changes until session ends

Step-by-Step Solution

Solution:

Step 1: Understand COMMIT effect
COMMIT permanently saves all changes and closes the transaction.
Step 2: Effect on ROLLBACK
After COMMIT, no active transaction exists, so ROLLBACK cannot undo changes.
Final Answer:
Because COMMIT permanently saves changes, ending the transaction -> Option C
Quick Check:
COMMIT ends transaction; ROLLBACK after has no effect [OK]

Quick Trick: COMMIT ends transaction; ROLLBACK after can't undo [OK]

Common Mistakes:

Master "Transactions and Data Integrity" in SQL

9 interactive learning modes - each teaches the same concept differently

More SQL Quizzes

Why does a ROLLBACK command not undo changes after a COMMIT in a transaction?