Performance Tuning with SQL Server Dynamic Management Views

Chapter 4: Transactions
BEGIN TRANSACTION
SELECT DTST.[session_id] ,
DTST.[transaction_id] ,
DTST.[is_user_transaction]
FROM sys.[dm_tran_session_transactions] AS DTST
WHERE DTST.[session_id] = @@SPID
ORDER BY DTST.[transaction_id]
COMMIT
session_id transaction_id is_user_transaction
----------- -------------------- -------------------
56 1550381 1
(1 row(s) affected)
Listing 4.10: Basic query against sys.dm_tran_session_transactions for transactions
on the current session.
sys.dm_tran_active_transactions
The sys.dm_tran_active_transactions DMV returns a list of all transactions
that are active at the time the query is executed. This view operates at the scope of the
entire SQL instance, meaning that results are returned for all databases on the instance.
Since this view provides a point-in-time snapshot of currently active transactions, the
results will change each time the query is executed, depending upon the state of the
individual transactions.
Identification columns returned by this view are transaction_id, which uniquely
identifies a transaction across the entire SQL Server instance, and name, which is the
name of the transaction. I consider it a good habit, if not a best practice, to name
transactions, as the following code snippet demonstrates:
BEGIN TRANSACTION Trans_Name
--Some SQL Code goes here
COMMIT TRANSACTION Trans_Name
140