In this post, I am sharing the use of SQL Server IMPLICIT TRANSACTIONS.

When you set the IMPLICIT TRANSACTION, database engine automatically considers a new transaction after every COMMIT/ROLLBACK.
We are writing DML statements between BEGIN and COMMIT/ROLLBACK. If our logic is divided into the different batches, managing BEGIN…COMMIT is difficult.

Just, you can set IMPLICIT TRANSACTION, and do COMMIT/ROLLBACK for each of your batches.

Note: Once you set IMPLICIT TRANSACTION, all your query tables will lock because IMPLICIT TRANSACTION applies the standard lock on the table. I can see only one feature is, not require to write BEGIN TRANSACTION that’s it.

Check the below demonstration:

Set IMPLICIT TRANSACTION:

SET IMPLICIT_TRANSACTIONS ON
GO

Create a sample table:

CREATE TABLE tbl_TestTransactions (ID INT, Name VARCHAR(10))
GO

Do COMMIT:

COMMIT TRANSACTION
GO

Now insert a sample record and do ROLLBACK:

INSERT INTO tbl_TestTransactions VALUES (1,'Anvesh')
ROLLBACK TRANSACTION 
GO

Test one more COMMIT:

INSERT INTO tbl_TestTransactions VALUES (2,'Roy')
COMMIT TRANSACTION
GO

Try ROLLBACK:
You will get an error because above there is no any open transaction.

ROLLBACK TRANSACTION
GO

Msg 3903, Level 16, State 1, Line 18
The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION.

Try one more ROLLBACK:

INSERT INTO tbl_TestTransactions VALUES (3,'Jenny')
GO
ROLLBACK TRANSACTION
GO

Check the final result:

SELECT *FROM tbl_TestTransactions

ID          Name
----------- ----------
2           Roy