Paweł Domański
25 lines
1.9 KiB
SQL
25 lines
1.9 KiB
SQL
--A long running transaction may prevent cleanup of transaction log thus eating up all log space available resulting space crisis for all other applications.
|
|
|
|
SELECT
|
|
transaction_id AS [Transacton ID],
|
|
[name] AS [TRANSACTION Name],
|
|
transaction_begin_time AS [TRANSACTION BEGIN TIME],
|
|
DATEDIFF(mi, transaction_begin_time, GETDATE()) AS [Elapsed TIME (in MIN)],
|
|
CASE transaction_type
|
|
WHEN 1 THEN 'Read/write'
|
|
WHEN 2 THEN 'Read-only'
|
|
WHEN 3 THEN 'System'
|
|
WHEN 4 THEN 'Distributed'
|
|
END AS [TRANSACTION Type],
|
|
CASE transaction_state
|
|
WHEN 0 THEN 'The transaction has not been completely initialized yet.'
|
|
WHEN 1 THEN 'The transaction has been initialized but has not started.'
|
|
WHEN 2 THEN 'The transaction is active.'
|
|
WHEN 3 THEN 'The transaction has ended. This is used for read-only transactions.'
|
|
WHEN 4 THEN 'The commit process has been initiated on the distributed transaction. This is for distributed transactions only. The distributed transaction is still active but further processing cannot take place.'
|
|
WHEN 5 THEN 'The transaction is in a prepared state and waiting resolution.'
|
|
WHEN 6 THEN 'The transaction has been committed.'
|
|
WHEN 7 THEN 'The transaction is being rolled back.'
|
|
WHEN 8 THEN 'The transaction has been rolled back.'
|
|
END AS [TRANSACTION Description]
|
|
FROM sys.dm_tran_active_transactions |