Month: February 2025

⚠️When a transaction is active, SQL Server locks affected tables and rows, preventing other queries from modifying them until the transaction is committed or rolled back. Long-running transactions can cause blocking, deadlocks, and performance issues, especially in high-traffic databases.

Understanding Transactions in T-SQL: BEGIN, ROLLBACK, and COMMIT

When working with Microsoft SQL Server, data integrity is crucial. Imagine running an update query on a production database and realizing midway that something is wrong—without transactions, your partial changes would be saved, potentially causing data corruption. That’s where T-SQL transactions come in.

Transactions in SQL Server allow you to group multiple operations into a single unit. If all operations succeed, the changes are committed; if something fails, you can roll back to ensure no partial updates occur. Let’s dive into the three key transaction commands: BEGIN TRANSACTION, COMMIT, and ROLLBACK.

1. BEGIN TRANSACTION

The BEGIN TRANSACTION statement marks the start of a transaction. From this point forward, SQL Server tracks all changes until you either commit them (COMMIT TRANSACTION) or undo them (ROLLBACK TRANSACTION).

Example: Starting a Transaction

BEGIN TRANSACTION; UPDATE Employees SET Salary = Salary * 1.10 WHERE Department = 'IT';

At this stage, the salary updates are made but not yet saved. If an error occurs or if we decide to cancel, we can roll back to the previous state.

2. COMMIT TRANSACTION

Once you’re satisfied that all operations in the transaction were successful, you use COMMIT TRANSACTION to make the changes permanent.

Example: Committing a Transaction

BEGIN TRANSACTION; UPDATE Employees SET Salary = Salary * 1.10 WHERE Department = 'IT'; COMMIT TRANSACTION;

Now, the salary changes are saved, and they cannot be undone.

3. ROLLBACK TRANSACTION

If something goes wrong, you can revert all changes made since BEGIN TRANSACTION using ROLLBACK TRANSACTION. This ensures data integrity by preventing partial updates.

Example: Rolling Back a Transaction

BEGIN TRANSACTION; UPDATE Employees SET Salary = Salary * 1.10 WHERE Department = 'IT'; -- Simulating an error IF @@ERROR <> 0      ROLLBACK TRANSACTION; ELSE       COMMIT TRANSACTION;

In this case, if an error occurs, the changes are discarded, and the database remains unchanged.

4. Using TRY…CATCH for Safe Transactions

To handle errors properly, wrap transactions in a TRY…CATCH block.

Example: Safe Transaction Handling

BEGIN TRANSACTION; BEGIN TRY     UPDATE Employees SET Salary = Salary * 1.10 WHERE Department = 'IT';     COMMIT TRANSACTION; END TRY   BEGIN CATCH     PRINT 'Error occurred. Rolling back changes.';     ROLLBACK TRANSACTION; END CATCH;

If any part of the transaction fails, it will be rolled back automatically.

5. Nested Transactions (Be Careful!)

SQL Server allows nested transactions, but only the outermost COMMIT TRANSACTION truly saves the changes. Rolling back anylevel undoes everything.

BEGIN TRANSACTION;   UPDATE Employees SET Salary = Salary * 1.10 WHERE Department = 'IT';     BEGIN TRANSACTION;       UPDATE Employees SET Bonus = Bonus + 500 WHERE Department = 'IT';     COMMIT TRANSACTION; ROLLBACK TRANSACTION; -- This undoes all changes, including the bonus update.

Even though we committed the inner transaction, the rollback at the outer level undoes everything.

Conclusion

Using transactions in T-SQL ensures data consistency and integrity. Always wrap critical updates in BEGIN TRANSACTION, and use ROLLBACK when things go wrong. If you’re running production queries, consider using TRY…CATCH to prevent data disasters.

By mastering BEGIN, COMMIT, and ROLLBACK, you gain full control over your SQL operations—ensuring changes only persist when everything runs smoothly.

Have you ever had to roll back a bad update? Let me know in the comments!