SQL Server searches for uncommitted transactions for a long time

Whether intentionally or unintentionally, if the transaction remains open in the database, it will block other processes from performing operations on the modified data. Similarly, backing up transaction logs will only truncate the transaction logs of non-active transactions, so opening transactions will lead to more logs (or even reach the physical limit ), until the transaction is committed or rolled back. Find the earliest event

Whether intentionally or unintentionally, if the transaction remains open in the database, it will block other processes from performing operations on the modified data. Similarly, backing up transaction logs will only truncate the transaction logs of non-active transactions, so opening transactions will lead to more logs (or even reach the physical limit ), until the transaction is committed or rolled back. Find the earliest event

Whether intentionally or unintentionally, if the transaction remains open in the database, it will block other processes from performing operations on the modified data. Similarly, backing up transaction logs will only truncate the transaction logs of non-active transactions, so opening transactions will lead to more logs (or even reach the physical limit ), until the transaction is committed or rolled back.

To find the earliest active transaction, you can use the dbcc opentran command.

An example is provided:

The Code is as follows: