SQL Server XTP (In-Memory OLTP) Performance Counters
Updated: April 6, 2016
THIS TOPIC APPLIES TO: SQL Server (starting with 2016)Azure SQL DatabaseAzure SQL Data Warehouse Parallel Data Warehouse
SQL Server provides objects and counters that can be used by Performance Monitor to monitor In-Memory OLTP activity. The objects and counters are shared across all instances of a given version of SQL Server on the machine, starting in SQL Server 2014.
In the past the object and counter names began with XTP, as in XTP Cursors. Now starting with SQL Server 2016, the names are like the following pattern:
- SQL Server <version> XTP Cursors
For <version> the value is something like 2016.
The following table describes SQL Server performance objects.
|SQL Server XTP Cursors||The SQL Server XTP Cursors performance object contains counters related to internal In-Memory OLTP engine cursors. Cursors are the low-level building blocks the In-Memory OLTP engine uses to process Transact-SQL queries. As such, you do not typically have direct control over them.|
|SQL Server XTP Garbage Collection||The SQL Server XTP Garbage Collection performance object contains counters related to the In-Memory OLTP engine's garbage collector.|
|SQL Server XTP Phantom Processor||The SQL Server XTP Phantom Processor performance object contains counters related to the In-Memory OLTP engine's phantom processing subsystem. This component is responsible for detecting phantom rows in transactions running at the SERIALIZABLE isolation level.|
|SQL Server XTP Storage||The SQL Server XTP Storage performance object contains counters related to In-Memory OLTP storage in SQL Server.|
|SQL Server XTP Transaction Log||The SQL Server XTP Transaction Log performance object contains counters related to In-Memory OLTP transaction logging in SQL Server.|
|SQL Server XTP Transactions||The SQL Server XTP Transactions performance object contains counters related to In-Memory OLTP engine transactions in SQL Server.|