SQL Server XTP Transactions object
Applies to:
SQL Server
The SQL Server XTP Transactions performance object contains counters related to transactions involving In-Memory OLTP in SQL Server.
This table describes the SQL Server XTP Transactions counters.
Counter | Description |
---|---|
Cascading aborts/sec | The number of transactions that rolled back to due a commit dependency rollback (on average), per second. |
Commit dependencies taken/sec | The number of commit dependencies taken by transactions (on average), per second. |
Read-only transactions prepared/sec | The number of read-only transactions that were prepared for commit processing, per second. |
Save point refreshes/sec | The number of times a savepoint was "refreshed", (on average), per second. A savepoint refresh is when an existing savepoint is reset to the current point in the transaction's lifetime. |
Save point rollbacks/sec | The number of times a transaction rolled back to a save point (on average), per second. |
Save points created/sec | The number of save points created (on average), per second. |
Transaction validation failure/sec | The number of transactions that failed validation processing (on average), per second. |
Transactions aborted by user/sec | The number of transactions that were aborted by the user (on average), per second. |
Transactions aborted/sec | The number of transactions that aborted (both by the user and the system, on average), per second. |
Transactions created/sec | The number of transactions created in the system (on average), per second. XTP transactions are counted differently than disk-based transactions (as reflected in Databases:Transactions/sec). For example, Transactions created/sec counts read/only transactions, while Databases:Transactions/sec does not. |
Examples
You begin to explore the query performance counters in this object using this T-SQL query on the sys.dm_os_performance_counters dynamic management view:
SELECT * FROM sys.dm_os_performance_counters
WHERE object_name LIKE '%XTP Transactions%';
Related content
Phản hồi
https://aka.ms/ContentUserFeedback.
Sắp ra mắt: Trong năm 2024, chúng tôi sẽ dần gỡ bỏ Sự cố với GitHub dưới dạng cơ chế phản hồi cho nội dung và thay thế bằng hệ thống phản hồi mới. Để biết thêm thông tin, hãy xem:Gửi và xem ý kiến phản hồi dành cho