Implicit transactions make SQL Server open a transaction on the first data statement and keep it open until a COMMIT or ROLLBACK. This post shows what starts one, how @@TRANCOUNT counts it, why a second session waits, and how to find and clear the sessions that left work open.
Long Running Queries in MySQL: Find Them in Two Ways
Find long running queries in MySQL with two built-in methods: the slow query log and the Performance Schema digest table. See the settings, a ready query and how to choose between them.
SAVE TRANSACTION: Roll Back Half a Transaction
SAVE TRANSACTION sets a marker inside an open transaction. You can roll back to it and keep the earlier work. This post tests it on SQL Server 2025. It shows why a nested BEGIN TRAN can’t do the same and what XACT_STATE() returns after an error.
SQL SERVER – NOLOCK with DMVs
NOLOCK with DMVs is not a blanket reassurance against monitoring waits. A customer asked about omitting the hint.
Before You KILL a Session: Estimating the Rollback Cost
Before you KILL a session, inspect its transaction age, log bytes, current command, and likely rollback work, then monitor the undo safely.
Finding the Indexes Behind Lock Waits With Operational Stats
Rank indexes behind lock waits with operational stats, separate latches from locks, and test targeted access or row versioning fixes.
Deadlock Victim Selection: Protect One Transaction
Deadlock victim selection decides which of two blocked transactions SQL Server rolls back. This post shows the rules, sets DEADLOCK_PRIORITY on one procedure, reproduces a deadlock with two query windows, and shows what the setting cannot do. It ends with the two fixes that remove the deadlock itself.