Fully durable transactions mean that SQL Server will wait for a commit to be reported and the transaction to be written to the transaction log before returning control to the client. While it is waiting for the commit to be reported, SQL Server will block other transactions and sessions from accessing the resources it is updating.

Fully durable transactions will harden or write the transaction to the transaction log before returning control to the client. This is the default behavior in SQL Server. You should use this setting if you cannot tolerate data loss or poor performance in your system, which is not caused by write latency on the transaction log.

A fully durable transaction guarantees that once a commit succeeds, data changes made by the transaction are visible to other transactions in the system and durability is guaranteed on commit. The transaction is written to the log before control is returned to the client, which means that in the...