The Transactions event classes can be used to monitor the status of transactions.
| Event class | Description |
|---|---|
| DTCTransaction | Tracks Microsoft® Distributed Transaction Coordinator (MS DTC) coordinated transactions between two or more databases. |
| SQLTransaction | Tracks Transact-SQL BEGIN, COMMIT, SAVE, and ROLLBACK TRANSACTION statements. |
| TransactionLog | Tracks when transactions are written to the transaction log. |
Use the DTCTransaction event class to monitor the state of MS DTC transactions as they occur. This can be useful when testing an application that makes use of distributed transactions.
Monitor the SQLTransaction event class when testing your application stored procedures or triggers to determine, for example, when transactions are committed or rolled back.
Use the TransactionLog event class when you want to monitor activity in the Microsoft SQL Server™ transaction log, for example, when you want to find out the types of logging activity that are happening when testing your application.
These are the event-specific data columns for the Transactions event category.
| Event class | Data column | Description |
|---|---|---|
| DTCTransaction | Binary Data | Globally unique ID (GUID) (in hexadecimal), if available. |
| Event Sub Class | MS DTC state. For more information, see your MS DTC documentation. | |
| Text | GUID (in text), if available. | |
| SQLTransaction | Event Sub Class | Type of SQL transaction event (COMMIT or ROLLBACK). |
| Text | Name of the transaction, or user transaction if the transaction is unnamed. | |
| TransactionLog | Event Sub Class | Type of transaction log event, such as BEGINXACT(null). |