INFORMANT-SQLSERVER-V2: View SNMP OID List / Download MIB

The MIB module for informant SQL Server V2 entries. This module supports SQL Server 2005 and SQL Server 2008.

This table contains the list of Analysis Services instance names installed. The as2NameIndex is used to refer to all other Analysis Services SNMP entries.

Performance information for one Analysis Services name instance.

The index number associated with the instance name

The name of the Analysis Services installed instance.

Statistics related to Microsoft Analysis Services aggregation cache.

Performance information for one SQL Server name instance.

Current memory used by the aggregation cache, in KB.

Current number of cache entries.

Ratio of cache direct hits to cache lookups, for the period between obtaining counter values.

Rate of cache direct hits. Queries were answered from an existing cache entry.

Rate of evictions from the cache. This is per partition per cube per database. Typically due to background cleaner.

Rate of insertions into the cache. This is per partition per cube per database.

Rate of memory added to the cache, KB/sec.

Rate of cache lookups.

Rate of cache misses.

Total count of direct cache hits. Queries were answered from existing cache entries.

Evictions from the cache. This is per partition per cube per database. Typically due to background cleaner.

Total number of cache hits that returned an indexed iterator over the filtered results

Total number of cache hits that were unable to build an indexed iterator over the filtered results and had to build a new cache with the filtered results

Insertions into the cache. This is per partition per cube per database.

Total number of lookups into the cache.

Total count of cache misses.

Statistics related to Microsoft Analysis Services connections.

Performance information for one SQL Server name instance.

Current number of client connections established.

Current number of user sessions established.

Rate of connection failures.

Rate of connection requests. These are arrivals.

Rate of successful connection completions.

Total failed connection attempts.

Total connection requests. These are arrivals.

Total successful connections.

Statistics related to Microsoft Analysis Services Data Mining model processing.

Performance information for one SQL Server name instance.

Rate of processing cases.

Current number of models being processed

Statistics related to Microsoft Analysis Services Data Mining prediction.

Performance information for one SQL Server name instance.

Current number of Data Mining queries being actively worked on.

Rate of Data Mining prediction queries

Rate of Data Mining queries

Rate of predicting rows

Total Data Mining Prediction Queries received by the server

Total Data Mining Queries received by the server

Total Rows returned by Data Mining queries

Statistics related to Microsoft Analysis Services internal server locks.

Performance information for one SQL Server name instance.

Current number of threads waiting for a latch. These are latch requests that could not be given immediate grants and are in a wait state.

Current number of clients waiting for a lock.

Current number of locked objects.

Rate of latch requests that could not be granted immediately and had to wait before being granted.

Rate of lock denials.

Number of lock grants per second.

Number of lock requests per second.

Number of lock waits per second. These are lock requests that could not be given immediate lock grants and were put in a wait state.

Total number of deadlocks detected.

Number of unlock requests per second.

Statistics related to Microsoft Analysis Services MDX Calculations.

Performance information for one SQL Server name instance.

Current (approximate) number of cached evaluation nodes built by MDX execution plans

Current (approximate) number of evaluation nodes built by MDX execution plans including active and cached

Total number of Storage Engine evaluation nodes built by MDX execution plans

Total number of bulk-mode evaluation nodes built by MDX execution plans

Total number of cached evaluation nodes built by MDX execution plans that are neither Storage Engine nor Bulk-mode

Total number of cached Storage Engine evaluation nodes built by MDX execution plans

Total number of cached bulk-mode evaluation nodes built by MDX execution plans

Total number of evaluation nodes built by MDX execution plans including active and cached

Total number of cell-by-cell evaluation nodes built by MDX execution plans

Total number of cell-by-cell hits in the cache of evaluation nodes

Total number of cell-by-cell misses in the cache of evaluation nodes

Total number of evaluation nodes built by MDX execution plans that covered only one cell

Total number of evaluation nodes built by MDX execution plans for which the calculations were at the same granularity as the evaluation node

Total number of cache evictions of evaluation nodes due to collisions

Total number of hits in the cache of evaluation nodes that were satisfied by the hash index

Total number of subcube hits in the cache of evaluation nodes

Total number of subcube misses in the cache of evaluation nodes

Total number of times autoexist performed

Total number of times EXISTING set operator performed

Total number of times NON EMPTY algorithms is used

Total number of times NON EMPTY algorithm was looping over calculated members

Total number of times unoptimized NON EMPTY algorithm is used

Total number of subcubes that query optimizer generated

Total number of cell properties calculated

Total number of cell values inserted into flat calculation cache

Total number of cells recomputed due to error

Statistics related to Microsoft Analysis Services internal server memory.

Performance information for one SQL Server name instance.

Current memory allocated to filestore (file cache), in KB.

Number of aggregation map files.

Rate of balance+shrink operations.

Current price of memory, $/byte/time, normalized to 1000.

Amount of memory, in KB, known to the background cleaner. (Cleaner memory shrinkable + Cleaner memory nonshrinkable.)

Amount of memory, in KB, not subject to purging by the background cleaner.

Amount of memory, in KB, subject to purging by the background cleaner.

Rate of shrinking, in KB/sec.

Number of dimension index (hash) files.

Number of dimension property files.

Number of dimension string files.

Number of fact aggregation files.

Number of fact data files.

Number of fact string files.

Rate of background cleaner examining pages for eviction consideration.

Rate of background cleaner examining pages that have a current reference count (are currently in use).

Rate of background cleaner examining pages that are valid candidates for eviction.

Filestore IO Errors total.

Filestore IO Error rate.

Current memory allocated to filestore (file cache), in KB.

Filestore KB read/sec.

Filestore KB written/sec. The writes are asynchronous.

Current filestore memory pinned KB.

Filestore page fault rate.

Filestore pages read/sec.

Filestore pages written/sec. The writes are asynchronous.

Current in-memory aggregation map file KB.

In-memory aggregation map file KB rate.

Current in-memory dimension index (hash) file KB.

In-memory dimension index (hash) file KB rate.

Current in-memory dimension proty file KB.

In-memory dimension proty file KB rate.

Current in-memory dimension string file KB.

In-memory dimension string file KB rate.

Current in-memory fact aggregation file KB.

In-memory fact aggregation file KB rate.

Current in-memory fact data file KB.

In-memory fact data file KB rate.

Current in-memory fact string file KB.

In-memory fact string file KB rate.

Current in-memory map file KB.

In-memory map file KB rate.

Current in-memory other file KB.

In-memory other file KB rate.

Number of map files.

High memory limit, from configuration file.

Low memory limit, from configuration file.

Memory usage of the server process. Same as perfmon counter for Process\PrivateBytes.

Number of other files.

Memory borrowed from 64KB page pool, in KB. This memory is given away to other parts of the server.

Current memory in 8KB lookaside list, in KB. (Memory pages ready to be used.)

Memory borrowed from system, in KB. This memory is given away to other parts of the server.

Current memory in 64KB lookaside list, in KB. (Memory pages ready to be used.)

Memory borrowed from 64KB page pool, in KB. This memory is given away to other parts of the server.

Current memory in 8KB lookaside list, in KB. (Memory pages ready to be used.)

Potential in-memory aggregation map file KB.

Potential in-memory dimension index (hash) file KB.

Potential in-memory dimension proty file KB.

Potential in-memory dimension string file KB.

Potential in-memory fact aggregation file KB.

Potential in-memory fact data file KB.

Potential in-memory fact string file KB.

Potential in-memory map file KB.

Potential in-memory other file KB.

Current number of quota requests that are blocked until other memory quotas are freed.

Current memory quota, in KB. Memory quota is also known as a memory grant or memory reservation.

Statistics related to Microsoft Analysis Services Proactive Caching.

Performance information for one SQL Server name instance.

Rate of notifications from relational database.

Rate of proactive caching begin.

Rate of proactive caching completion.

Rate of processing cancellations caused by notifications.

Statistics related to Microsoft Analysis Services processing of aggregations in MOLAP data files.

Performance information for one SQL Server name instance.

Current number of partitions being processed.

Size of current aggregations in memory. This count is an estimate.

Size of current aggregations in memory. This count is an estimate.

Rate of aggregation rows created.

Rate of rows merged or inserted into an aggregation.

Rate of writing bytes to a temporary file. Temporary files are written when aggregations exceed memory limits.

Rate of writing rows to a temporary file. Temporary files are written when aggregations exceed memory limits.

Total number of partitions processed (successfully or otherwise).

Statistics related to Microsoft Analysis Services processing of indexes for MOLAP data files.

Performance information for one SQL Server name instance.

Current number of partitions being processed.

Rate of rows from MOLAP files used to create indexes.

Total number of partitions processed (successfully or otherwise).

Total rows from MOLAP files used to create indexes.

Statistics related to Microsoft Analysis Services processing of data.

Performance information for one SQL Server name instance.

Rate of rows converted during processing.

Rate of rows read from all relational databases.

Rate of rows written during processing.

Count of rows converted during processing.

Count of rows read from all relational databases.

Count of rows written during processing.

Statistics related to Microsoft Analysis Services storage engine queries.

Performance information for one SQL Server name instance.

Rate of aggregation hits.

Rate of aggregation lookups.

Average time per query, in milliseconds. Response time based on queries answered since the last counter measurement.

Rate of bytes sent by server to clients, in response to queries.

Rate of calculation cache hits. This includes global, session, and query scope calculation caches.

Rate of calculation cache lookups. This includes global, session, and query scope calculation caches.

Current number of dimension queries being actively worked on.

Current number of measure group queries being actively worked on.

Bytes read from the Data file.

Number of logical read operations using the Data file.

Rate of dimension cache hits.

Rate of dimension cache lookups.

Rate of dimension queries

Rate of flat cache hits. This includes global, session, and query scope flat caches.

Rate of flat cache lookups. This includes global, session, and query scope flat caches.

Bytes read from the Map file.

Number of logical read operations using the Map file.

Rate of measure group cache hits.

Rate of measure group cache lookups.

Rate of measure group queries

Rate of network round trips. This includes all client/server communication.

Rate of persisted cache hits. Persisted caches are created by the MDX script CACHE statement.

Rate of sisted cache lookups. sisted caches are created by the MDX script CACHE statement.

Rate of queries answered.

Rate of queries answered from cache directly.

Rate of queries answered by filtering existing cache entry.

Rate of queries answered from files.

Rate of rows sent by server to clients.

Total bytes sent by server to clients, in response to queries.

Total number of dimension queries.

Total number of queries to measure group.

Total network round trips. This includes all client/server communication.

Total number of queries answered.

Total number of queries derived directly from cache. Note that this is partition.

Total queries answered by filtering existing cache entries.

Total number of queries answered from files.

Total rows sent by server to clients.

Statistics related to Microsoft Analysis Services threads.

Performance information for one SQL Server name instance.

Number of busy threads in the long parsing thread pool.

Number of idle threads in the long parsing thread pool.

Number of jobs in the queue of the long parsing thread pool.

Rate of jobs through the long parsing thread pool.

Number of busy threads in the processing thread pool.

Number of idle threads in the processing thread pool.

Number of jobs in the queue of the processing thread pool.

Rate of jobs through the processing thread pool.

Number of busy threads in the query thread pool.

Number of idle threads in the query thread pool.

Number of jobs in the queue of the query thread pool.

Rate of jobs through the query thread pool.

Number of busy threads in the short parsing thread pool.

Number of idle threads in the short parsing thread pool.

Number of jobs in the queue of the short parsing thread pool.

Rate of jobs through the short parsing thread pool.

This table contains the list of SQL Server instance names installed. The ss2NameIndex is used to refer to all other SQL Server SNMP entries.

Performance information for one SQL Server name instance.

The index number associated with the instance name

The name of the SQL Server installed instance.

The Access Methods object in SQL Server provides counters to monitor how the logical data within the database is accessed. Physical access to the database pages on disk is monitored using the Buffer Manager counters. Monitoring the methods used to access data stored in the database can help you to determine whether query performance can be improved by adding or modifying indexes, adding or moving partitions, adding files or file groups, defragmenting indexes, or by rewriting queries. The Access Methods counters can also be used to monitor the amount of data, indexes, and free space within the database, thereby indicating data volume and fragmentation for each server instance. Excessive index fragmentation can impair performance.

Performance information for one SQL Server AccessMethods instance.

The number of batches that completed successfully per second by the background task that cleans up deferred dropped allocation units.

The number of allocation units per second that were successfully dropped by the background task that cleans up deferred dropped allocation units. Each allocation unit drop requires multiple batches.

Count of large object (LOB) values that were passed by reference. By-reference lobs are used in certain bulk operations to avoid the cost of passing them by value.

Count of by-reference lob values that were used. By-reference lobs are used in certain bulk operations to avoid the cost of passing them by value.

Count of lob pages on which readahead was issued.

Count of values that were pulled in-row from off-row.

Count of values that were pushed from in-row to off-row.

The number of rowsets created as a result of aborted online index build operations that are waiting to be dropped by the background task that cleans up deferred dropped rowsets.

The number of allocation units waiting to be dropped by the background task that cleans up deferred dropped allocation units.

The number of rowsets per second created as a result of aborted online index build operations that were successfully dropped by the background task that cleans up deferred dropped rowsets.

The number of rowsets per second created as a result of aborted online index build operations that were skipped by the background task that cleans up deferred dropped rowsets created.

Number of extents deallocated per second in all databases in this SQL Server instance.

Number of extents allocated per second in all databases in this SQL Server instance.

The number of batches second that failed and required retry, by the background task that cleans up deferred dropped allocation units. Failure could be due to lack of memory or disk space, hardware failure and other reasons.

The number of times that a leaf page cookie could not be used during an index search since changes happened on the leaf page. The cookie is used to speed up index search.

The number of times that a tree page cookie could not be used during an index search since changes happened on the parent pages of those tree pages. The cookie is used to speed up index search.

Number of records fetched through forwarded record pointers.

Number of pages fetched per second by free space scans. These scans search for free space within pages already allocated to an allocation unit, to satisfy requests to insert or modify record fragments.

Number of scans per second that were initiated to search for free space within pages already allocated to an allocation unit to insert or modify record fragments. Each scan may find multiple pages.

Number of unrestricted full scans. These can either be base table or full index scans.

Number of index searches. Index searches are used to start range scans, single index record fetches, and to reposition within an index.

Count of temporary LOBs created.

Count of temporary LOBs destroyed.

Count of LOB Storage Service Providers created. One worktable created per LOB Storage Service Provider.

Count of LOB Storage Service Providers destroyed.

Count of LOB Storage Service Providers truncated.

Number of pages allocated per second from mixed extents. These could be used for storing the IAM pages and the first eight pages that are allocated to an allocation unit.

Number of pages deallocated per second in all databases in this SQL Server instance. These include pages from mixed extents and uniform extents.

Number of page splits per second that occur as a result of overflowing index pages.

Number of attempts to compress a database page second

Number of pages allocated per second in all databases in this SQL Server instance. These include pages allocations from both mixed extents and uniform extents.

Number of times a database page was compressed

Number of probe scans per second that are used to find at most one single qualified row in an index or base table directly.

Number of qualified range scans through indexes per second.

Number of times the scan point had to be revalidated to continue the scan.

Number of ghosted records per second skipped during scans.

The number of times locks on a table were escalated.

Number of times a leaf page cookie was used successfully during an index search since no change happened on the leaf page. The cookie is used to speed up index search.

Number of times a tree page cookie was used successfully during an index search since no change happened on the parent page of the tree page. The cookie is used to speed up index search.

Number of work files created per second. For example, work files could be used to store temporary results for hash joins and hash aggregates.

Number of work tables created per second. For example, work tables could be used to store temporary results for query spool, LOB variables, XML variables, and cursors.

Percentage of work tables created where the initial two pages of the work table were not allocated but were immediately available from the work table cache.

The Backup Device object provides counters to monitor Microsoft SQL Server backup devices used for backup and restore operations. Monitor backup devices when you want to determine the throughput or the progress and performance of your backup and restore operations on a per device basis. To monitor the throughput of the entire database backup or restore operation, use the Backup/Restore Throughput/sec counter of the SQL Server Databases object.

Performance information for one particular instance of 'Backup Device' object.

Instance name.

Read/write throughput for a backup device.

The BrokerActivation performance object contains performance counters that report information on stored procedure activation.

Performance information for one particular instance of 'Broker Activation' object.

Instance name.

The number of stored procedures that are being invoked second.

The total number of times the activated task limit on a queue has been reached.

The number of times the activated task limit on a queue has been reached per second.

The number of activated tasks that are being aborted per second.

The total number of activated tasks that are currently running.

The number of activated tasks that are being started per second.

The Broker Statistics performance object contains performance counters that report general Service Broker information for an instance of the Database Engine.

Performance information for one SQL Server BrokerStatistics instance.

The number of times an activation stored procedure exited with an error.

The number of Service Broker related transactions that have rolled back.

The number of corrupted messages that were received in the instance.

The number of messages that have been removed from the broker transmission queue second.

The number of dialog endpoint related timer events in the Broker.

The number of messages that were received in the instance but could not be delivered.

Total number of messages from local endpoints that are successfully delivered directly into local target queues.

The number of messages from local endpoints that are successfully delivered directly into local target queues per second.

Total number of messages from local endpoints and the transport that are successfully delivered into local target queues.

The number of messages from local endpoints and the transport that are successfully delivered into local target queues per second.

The number of priority 1 messages from local endpoints and the transport that are successfully delivered into local target queues per second.

The number of priority 10 messages from local endpoints and the transport that are successfully delivered into local target queues per second.

The number of priority 2 messages from local endpoints and the transport that are successfully delivered into local target queues per second.

The number of priority 3 messages from local endpoints and the transport that are successfully delivered into local target queues per second.

The number of priority 4 messages from local endpoints and the transport that are successfully delivered into local target queues per second.

The number of priority 5 messages from local endpoints and the transport that are successfully delivered into local target queues per second.

The number of priority 6 messages from local endpoints and the transport that are successfully delivered into local target queues per second.

The number of priority 7 messages from local endpoints and the transport that are successfully delivered into local target queues per second.

The number of priority 8 messages from local endpoints and the transport that are successfully delivered into local target queues per second.

The number of priority 9 messages from local endpoints and the transport that are successfully delivered into local target queues per second.

The number of messages that have been placed into the broker transmission queue second.

Total number of message fragments from the transport that are successfully delivered into local target queues. Note that the message can be marked as disabled if it is incomplete and/or out of order.

The number of message fragments from the transport that are successfully delivered into local target queues second. Note that the message can be marked as disabled if it is incomplete and/or out of order.

Total number of messages from the transport that are successfully delivered into local target queues. This includes all messages from remote endpoints and messages from local endpoints which go through the transport.

The number of messages from the transport that are successfully delivered into local target queues per second. This includes all messages from remote endpoints and messages from local endpoints which go through the transport.

Total number of forwarded messages successfully sent.

The number of forwarded messages successfully sent per second.

Total number of forwarded message bytes successfully sent.

The number of forwarded message bytes successfully sent per second.

Total number of forwarded messages discarded due to forwarded message memory limits, age limits, etc.

The number of forwarded messages that were discarded second due to forwarded message memory limits, age limits, etc.

The number of forwarded message bytes that have not been successfully sent yet.

The number of forwarded messages that have not been successfully sent yet.

Total number of SQL RECEIVE commands processed by the Broker.

The number of SQL RECEIVE commands processed by the Broker per second.

Total number of SQL SEND commands processed by the Broker.

The number of SQL SEND commands processed by the Broker per second.

The Broker TO Statistics performance object reports information about how many times Service Broker dialogs request transmission objects, and how often transmission objects are written to tempdb. Transmission objects record the state of message transmissions for a Service Broker dialog. They are stored in memory. To free memory, Service Broker periodically writes batches of inactive transmission objects to work tables in tempdb.

Performance information for one SQL Server BrokerTOStatistics instance.

Average Number of Transmission Objects saved in a batch.

Average time between Transmission Object batch flushes.

Average time to save a Transmission Object batch.

The number of Transmission Objects requested per second.

The number of Transmission Objects marked dirty second.

The number of Transmission Objects saved second.

The Broker / DBM Transport performance object contains performance counters that report networking information for Service Broker and database mirroring.

Performance information for one SQL Server BrokerPerDBMTransport instance.

The number of bytes associated with current transport receive I/O operations that haven't completed.

The number of buffer bytes associated with current transport send I/O operations that haven't completed.

The current number of message fragments associated with current transport send I/O oations that haven't completed.

The number of priority 1 message fragments sent second in transport send I/O oations.

The number of priority 10 message fragments sent second in transport send I/O oations.

The number of priority 2 message fragments sent second in transport send I/O oations.

The number of priority 3 message fragments sent second in transport send I/O oations.

The number of priority 4 message fragments sent second in transport send I/O oations.

The number of priority 5 message fragments sent second in transport send I/O oations.

The number of priority 6 message fragments sent second in transport send I/O oations.

The number of priority 7 message fragments sent second in transport send I/O oations.

The number of priority 8 message fragments sent second in transport send I/O oations.

The number of priority 9 message fragments sent second in transport send I/O oations.

The number of message fragments received second in transport receive I/O oations.

The number of message fragments sent per second in transport send I/O operations.

The average byte size of message fragments received in transport receive I/O operations.

The average byte size of message fragments sent in transport send I/O operations.

The total number of transport connections currently open.

The number of bytes associated with in completed transport receive I/O operations whose message fragments haven't been enqueued (or rejected) yet.

The number of buffer bytes associated with message fragments being marshalled, or marshalled and ready to be sent with send I/O operations.

The current number of message fragments received in transport receive I/O oations that have not been enqueued (or rejected) yet.

The current number of message fragments that are being marshalled, or marshalled and ready to be sent via the transport layer.

The average byte length of transport receive I/O operations.

The number of transport receive I/O bytes per second.

The number of transport receives I/O per second. Note that a transport receive I/O may contain more than one message fragment.

The number of times when transport receive I/O operations had to move buffer fragments in memory.

The rate at which transport receive I/O oations had to move buffer fragments in memory.

The average byte length of transport send I/O operations.

The number of transport send I/O bytes per second.

The number of transport send I/Os per second. Note that a transport send I/O may contain more than one message fragment.

The Buffer Manager object provides counters to monitor how SQL Server uses: * Memory to store data pages, internal data structures, and the procedure cache. * Counters to monitor the physical I/O as SQL Server reads and writes database pages. Monitoring the memory and the counters used by SQL Server helps you determine: * If bottlenecks exist from inadequate physical memory. If it cannot store frequently accessed data in cache, SQL Server must retrieve the data from disk. * If query performance can be improved by adding more memory, or by making more memory available to the data cache or SQL Server internal structures. * How often SQL Server needs to read data from disk. Compared with other operations, such as memory access, physical I/O consumes a lot of time. Minimizing physical I/O can improve query performance. You can also monitor Address Windowing Extensions (AWE) activity in SQL Server with the AWE counters. For example, you can make sure that SQL Server has enough memory allocated for AWE to run properly.

Performance information for one SQL Server BufferManager instance.

Number of AWE map calls made for pages found in the buffer pool.

Number of AWE map calls made for pages stolen from the buffer pool.

Number of AWE unmap calls.

Number of AWE pages unmapped.

Number of AWE map calls made for pages to be written to disk.

Percentage of pages that were found in the buffer pool without having to incur a read from disk.

Number of pages flushed by checkpoint or other operations that require all dirty pages to be flushed.

Number of pages in the buffer pool with database content.

Number of requests that had to wait for a free page.

Total number of pages on all free lists.

Number of buffers written by buffer manager's lazy writer.

Number of seconds a page will stay in the buffer pool without references.

Number of requests to find a page in the buffer pool.

Number of physical database page reads issued.

Number of physical database page writes issued.

Number of pages read in anticipation of use.

Number of buffer pool reserved pages.

Number of pages used for miscellaneous server purposes (including procedure cache).

Ideal number of pages in the buffer pool.

Number of pages in the buffer pool (includes database, free, and stolen).

The Buffer Node object provides counters that complement counters provided by the Buffer Manager object. It allows you to monitor the SQL Server buffer pool page distribution for each non-uniform memory access (NUMA) node. There is an instance of the Buffer Node object for each NUMA node in use. On non-NUMA architecture there will be a single instance of the Buffer Node object.

Performance information for one particular instance of 'Buffer Node' object.

Instance name.

Number of pages in the buffer pool with database content.

Number of pages which are not from NUMA-local memory.

Total number of pages on all free lists.

Number of lookup requests from this node which were satisfied from this node.

Number of seconds a page will stay in the buffer pool without references.

Number of lookup requests from this node which were satisfied from other nodes.

Number of pages used for miscellaneous server purposes (including procedure cache).

Ideal number of pages in the buffer pool.

Number of pages in the buffer pool (includes database, free, and stolen).

The Buffer Partition object provides counters to monitor how SQL Server uses free pages.

Performance information for one particular instance of 'Buffer Partition' object.

Instance name.

Number of times a free page was requested and none were available.

Number of times a free page was requested.

Total number of pages on all free lists.

The CLR object provides counters to monitor common language runtime (CLR) execution in Microsoft SQL Server.

Performance information for one SQL Server CLR instance.

Total Execution time in CLR ( microseconds ).

A table containing performance information for instances of 'Catalog Metadata' objects.

Performance information for one particular instance of 'Catalog Metadata' object.

Instance name.

Number of entries in the catalog metadata cache

Number of catalog metadata cache entries that are pinned

Ratio between cache hits and lookups

The Cursor Manager Total object provides counters to monitor cursors.

Performance information for one particular instance of 'Cursor Manager by Type' object.

Number of cursors being populated asynchronously.

Number of cursor conversions/sec.

Total number of times a flush for a cursor xstmt occured.

The Cursor Manager by Type object provides counters to monitor cursors, grouped by type.

Performance information for one particular instance of 'Cursor Manager by Type' object.

Instance name.

Number of active cursors.

Ratio between cache hits and lookups

Number of cursors of a given type in the cache

Times each type of cached cursor has been used

Number of SQL cursor requests received by server.

Amount of memory consumed by cursors (KB).

Number of worktables used by cursors.

Number of cursor plans.

The Database Mirroring performance object contains performance counters that report information about SQL Server database mirroring.

Performance information for one particular instance of 'Database Mirroring' object.

Instance name.

Number of bytes received per second

Number of bytes sent per second

Number of bytes of log received per second

Number of log bytes which were redone from the Database Mirroring log cache second.

Number of sent log bytes which were sent from the Database Mirroring log cache in the last second.

Number of bytes of log sent per second

Number of compressed bytes of log received in the last second.

Number of compressed bytes of log sent in the last second.

Milliseconds log blocks waited to be hardened to disk in the last second.

Total number of kilobytes of log that remain to be scanned by the new mirror server after failover.

Total number of kilobytes of log that have been scanned by the new mirror server after failover.

Milliseconds log stream messages waited for send flow control in the last second.

Total number of kilobytes of log that have not been sent to the mirror server

Number of transactions which wrote to the mirrored database in the last second, that waited for log to be sent to the mirror.

Number of pages sent per second

Number of mirroring message receives per second

Number of bytes of log redone by the mirror database per second

Total number of kilobytes that redo on the mirror database is behind the hardened log

Milliseconds messages waited for acknowledgement from the partner per second.

Number of sends initiated per second

Number of milliseconds transaction termination waited for acknowledgement per second.

The Databases object in SQL Server provides counters to monitor bulk copy operations, backup and restore throughput, and transaction log activities. Monitor transactions and the transaction log to determine how much user activity is occurring in the database and how full the transaction log is becoming. The amount of user activity can determine the performance of the database and affect log size, locking, and replication. Monitoring low-level log activity to gauge user activity and resource usage can help you to identify performance bottlenecks. Multiple instances of the Databases object, each representing a single database, can be monitored at the same time.

Performance information for one particular instance of 'Databases' object.

Instance name.

Number of active update transactions for the database.

Read/write throughput for backup/restore of a database.

Number of rows bulk copied.

KiloBytes bulk copied.

The size of the in-memory part of the commit table for the database.

Logical read scan rate for DBCC commands

The cumulative size of all the data files in the database.

Total number of log bytes flushed.

Percentage of log cache reads that were satisfied from the log cache.

Reads performed through the log manager cache.

The cumulative size of all the log files in the database.

The cumulative used size of all the log files in the database.

Total wait time (milliseconds).

Number of commits waiting on log flush.

Number of log flushes.

Total number of log growths for this database.

Total number of log shrinks for this database.

Total number of log truncations for this database.

The percent of space in the log that is in use.

Number of pending replication transactions in the database.

Replication transaction rate (replicated transactions/sec.).

The rate data is being moved by Autoshrink, DBCC SHRINKDATABASE or SHRINKFILE.

Number of committed transactions recorded in the commit table for the database.

Number of transactions started for the database.

Number of transactions which wrote to the database in the last second.

The Deprecated Features object in SQL Server provides a counter to monitor the features designated as deprecated. In each case the counter provides a usage count that lists the number of times the deprecated feature was encountered since SQL Server last started.

Performance information for one particular instance of 'Deprecated Features' object.

Instance name.

Feature usage since last SQL Server startup

The ExecStatistics object in Microsoft SQL Server provides counters to monitor various executions.

Performance information for one particular instance of 'Exec Statistics' object.

Instance name.

Statistics relevant to execution of DTC calls.

Statistics relevant to execution of distributed queries.

Statistics relevant to execution of XP calls.

Statistics relevant to execution of OLEDB calls.

The General Statistics object in Microsoft SQL Server provides counters to monitor general server-wide activity, such as the number of current connections and the number of users connecting and disconnecting per second from computers running an instance of SQL Server. This can be useful when you are working on large online transaction processing (OLTP) type systems where there are many clients connecting and disconnecting from an instance of SQL Server.

Performance information for one SQL Server GeneralStatistics instance.

Number of temporary tables/table variables in use

Total number of connection resets per second.

Number of event notifications waiting to be dropped by a system thread

Number of authenticated HTTP requests started per second.

Number of logical connections to the system.

Total number of logins started per second.

Total number of logouts started per second.

Number of Mars Deadlocks detected.

Number of non-atomic yields per second.

Number of currently blocked processes.

Number of empty SOAP requests started per second.

Number of SOAP method invocations started per second.

Number of SOAP SQL requests started per second.

Number of SOAP Session initiate requests started per second.

Number of SOAP Session terminate requests started second.

Number of SOAP Web Service Description Language requests started per second.

Number of waits for the File IO Provider lock per second

Number of temporary tables/table variables created/sec

Number of temporary tables/table variables waiting to be destroyed by the cleanup system thread

Number of duplicate tempdb recovery unit id generated

Number of duplicate tempdb rowset id generated

Number of trace event notification instances waiting in the internal queue to be sent thru Service Broker

Number of transaction enlistments (local, dtc, and bound).

Number of users connected to the system.

The Latches object in Microsoft SQL Server provides counters to monitor internal SQL Server resource locks called latches. Monitoring the latches to determine user activity and resource usage can help you to identify performance bottlenecks.

Performance information for one SQL Server Latches instance.

Average latch wait time (milliseconds) for latch requests that had to wait.

Number of latch requests that could not be granted immediately and had to wait before being granted.

Number of latches that are currently SuperLatches.

Number of SuLatches that have been demoted to regular latches

Number of latches that have been promoted to SuLatches

Total latch wait time (milliseconds) for latch requests that had to wait in the last second.

The Locks object in Microsoft SQL Server provides information about SQL Server locks on individual resource types. Locks are held on SQL Server resources, such as rows read or modified during a transaction, to prevent concurrent use of resources by different transactions. For example, if an exclusive (X) lock is held on a row within a table by a transaction, no other transaction can modify that row until the lock is released. Minimizing locks increases concurrency, which can improve performance. Multiple instances of the Locks object can be monitored at the same time, with each instance representing a lock on a resource type.

Performance information for one particular instance of 'Locks' object.

Instance name.

The average amount of wait time (milliseconds) for each lock request that resulted in a wait.

Number of new locks and lock conversions requested from the lock manager.

Number of lock requests that timed out. This does not include requests for NOWAIT locks.

Number of lock requests that timed out. This includes requests for NOWAIT locks.

Total wait time (milliseconds) for locks in the last second.

Number of lock requests that could not be satisfied immediately and required the caller to wait before being granted the lock.

Number of lock requests that resulted in a deadlock.

The Memory Manager object in Microsoft SQL Server provides counters to monitor overall server memory usage. Monitoring overall server memory usage to gauge user activity and resource usage can help you to identify performance bottlenecks. Monitoring the memory used by an instance of SQL Server can help determine: * If bottlenecks exist from inadequate physical memory for storing frequently accessed data in cache. If memory is inadequate, SQL Server must retrieve the data from disk. * If query performance can be improved by adding more memory or by making more memory available to the data cache or SQL Server internal structures.

Performance information for one SQL Server MemoryManager instance.

Total amount of dynamic memory the server is using for maintaining connections

Total amount of memory granted to executing processes. This memory is used for hash, sort and create index operations.

The current number of lock blocks that are in use on the server. Refreshed periodically.

The current number of allocated lock blocks.

Total amount of dynamic memory the server is using for locks

The number of lock owner blocks that are currently in use on the server. Refreshed periodically.

The current number of allocated lock owner blocks.

Total amount of memory granted to executing processes. This memory is used primarily for hash, sort and create index operations.

Current number of processes that have successfully acquired a workspace memory grant

Current number of processes waiting for a workspace memory grant

Total amount of dynamic memory the server is using for query optimization

Total amount of dynamic memory the server is using for the dynamic SQL cache

Total amount of dynamic memory the server is willing to consume

Total amount of dynamic memory the server is currently consuming

The Plan Cache object provides counters to monitor how SQL Server uses memory to store objects such as stored procedures, ad hoc and prepared Transact-SQL statements, and triggers. Multiple instances of the Plan Cache object can be monitored at the same time, with each instance representing a different type of plan to monitor.

Performance information for one particular instance of 'Plan Cache' object.

Instance name.

Ratio between cache hits and lookups

Number of cache objects in the cache

Number of cache objects in use

Number of 8k pages used by cache objects

A table containing performance information for instances of 'Replication Agents' objects.

Performance information for one particular instance of 'Replication Agents' object.

Instance name.

The number of replication agents currently running.

A table containing performance information for instances of 'Replication Dist.' objects.

Performance information for one particular instance of 'Replication Dist.' object.

Instance name.

The number of commands per second delivered to the Subscriber.

The number of transactions per second delivered to the Subscriber.

The current amount of time, in milliseconds, elapsed from when transactions are delivered to the Distributor to when they are applied at the Subscriber.

A table containing performance information for instances of 'Replication Logreader' objects.

Performance information for one particular instance of 'Replication Logreader' object.

Instance name.

The number of commands second delivered to the Distributor.

The number of transactions second delivered to the Distributor.

The current amount of time, in milliseconds, elapsed from when transactions are applied at the Publisher to when they are delivered to the Distributor.

A table containing performance information for instances of 'Replication Merge' objects.

Performance information for one particular instance of 'Replication Merge' object.

Instance name.

The number of conflicts per second occurring during the merge process.

The number of rows per second merged from the Publisher to the Subscriber.

The number of rows per second merged from the Subscriber to the Publisher.

A table containing performance information for instances of 'Replication Snapshot' objects.

Performance information for one particular instance of 'Replication Snapshot' object.

Instance name.

The number of commands per second delivered to the Distributor.

The number of transactions second delivered to the Distributor.

A table containing performance information for instances of 'Resource Pool Stats' objects.

Performance information for one particular instance of 'Resource Pool Stats' object.

Instance name.

Total amount of granted memory in kilobytes in the resource pool.

Number of query memory grants in the resource pool.

Effect of the resource governor on the resource pool calculated as (CPU usage %) / (CPU usage % without RG).

System CPU usage by all requests in the specified instance of the performance object.

Target value of 'CPU usage %' for the resource pool based on the configuration settings and the system load.

Current memory target for cache memory in kilobytes.

Current memory target for query compile in kilobytes.

Maximum amount of memory in kilobytes the resource pool can have based on the settings and server state.

Number of query memory grant timeouts per second occurring in the resource pool.

Number of query memory grants per second occurring in the resource pool.

Number of queries waiting for memory grants in the resource pool.

Current memory target for query execution memory grant in kilobytes.

Target amount of memory in kilobytes the resource pool is trying to attain based on the settings and server state.

Used amount of memory in kilobytes in the resource pool.

The SQL Errors object in Microsoft SQL Server provides counters to monitor SQL Errors.

Performance information for one particular instance of 'SQL Errors' object.

Instance name.

Number of errors/sec

The SQL Statistics object in SQL Server provides counters to monitor compilation and the type of requests sent to an instance of SQL Server. Monitoring the number of query compilations and recompilations and the number of batches received by an instance of SQL Server gives you an indication of how quickly SQL Server is processing user queries and how effectively the query optimizer is processing the queries. Compilation is a significant part of a query's turnaround time. In order to save the compilation cost, the Database Engine saves the compiled query plan in a query cache. The objective of the cache is to reduce compilation by storing compiled queries for later reuse, therefore ending the requirement to recompile queries when later executed. However, each unique query must be compiled at least one time. Query recompilations can be caused by the following factors: * Schema changes, including base schema changes such as adding columns or indexes to a table, or statistics schema changes such as inserting or deleting a significant number of rows from a table. * Environment (SET statement) changes. Changes in session settings such as ANSI_PADDING or ANSI_NULLS can cause a query to be recompiled.

Performance information for one SQL Server SQLStatistics instance.

Number of auto-parameterization attempts.

Number of SQL batch requests received by server.

Number of failed auto-parameterizations.

Number of statements parameterized by forced parameterization second.

Number of plan executions per second in which the query plan has been generated by using a plan guide.

Number of plan executions second in which a plan guide could not be honored during plan generation. The plan guide was disregarded and normal compilation was used to generate the executed plan.

Number of attentions per second.

Number of SQL compilations.

Number of SQL re-compiles.

Number of safe auto-parameterizations.

Number of unsafe auto-parameterizations.

A table containing performance information for instances of 'SSIS Pipeline' objects.

Performance information for one particular instance of 'SSIS Pipeline' object.

The number of BLOB bytes read from all data sources in total.

The number of BLOB bytes written to all data sources in total.

The number of BLOB spooling files in use throughout the pipeline.

The amount of memory allocated to buffers in the pipeline.

The number of pipeline buffers in use throughout the pipeline.

The number of buffers spooled to disk.

The amount of memory allocated to flat memory buffers.

The number of flat memory buffers in use throughout the pipeline.

The amount of memory allocated to private transformation buffers.

The number of private transformation buffers in use throughout the pipeline.

The number of rows read from all data sources in total.

The number of rows written to all data destinations in total.

A table containing performance information for instances of 'SSIS Service' objects.

Performance information for one particular instance of 'SSIS Service' object.

The number of package instances currently running.

A table containing performance information for instances of 'Trace Event Statistics' objects.

Performance information for one particular instance of 'Trace Event Statistics' object.

Instance name.

Bytes transferred by this trace per second

CPU usage per second (Requires -T1904)

Events filtered per second

Events fired by this trace per second

Prefiltered events per second

A table containing performance information for instances of 'Trace Statistics' objects.

Performance information for one particular instance of 'Trace Statistics' object.

Instance name.

Bytes transferred by this trace per second

Events dropped by this trace per second

Events filtered per second

Events fired by this trace per second

The Transactions object in Microsoft SQL Server provides counters to monitor the number of transactions active in an instance of the Database Engine, and the effects of those transactions on resources such as the snapshot isolation row version store in tempdb. Transactions are logical units of work; a set of operations that must either all succeed or all be erased from a database in order to maintain the logical integrity of the data. All modifications of data in SQL Server databases are made in transactions. When a database is set to allow snapshot isolation level, SQL Server must maintain a record of the modifications made to each row in a database. Each time a row is modified, a copy of the row as it existed before the modification is recorded in a row version store in tempdb. Many of the counters in the Transaction object can be used to monitor the size and rate of growth of the row version store in tempdb. The Transactions object counters report all transactions in one instance of the Database Engine.

Performance information for one SQL Server Transactions instance.

The free space in tempdb in KB.

The longest running time of any transcation in seconds.

The total number of active non-snapshot transactions that generate version records.

The total number of active snapshot transactions.

Number of transaction enlistments (local, dtc, and bound).

The total number of active snapshot transactions that do updates.

The fraction of update snapshot transactions that have update conflicts to the total number of update snapshot transactions.

The version cleanup rate in KB per seconds.

The version generation rate in KB seconds.

The size of the version store in KB.

Number of unit in Version Store.

Creation of new unit in Version Store.

Truncation of unit in Version Store.

The User Settable object in Microsoft SQL Server allows you to create custom counter instances. Use custom counter instances to monitor aspects of the server not monitored by existing counters, such as components unique to your SQL Server database (for example, the number of customer orders logged or the product inventory). The User Settable object contains 10 instances of the query counter: User counter 1 through User counter 10. These counters map to the SQL Server stored procedures sp_user_counter1 through sp_user_counter10. As these stored procedures are executed by user applications, the values set by the stored procedures are displayed in System Monitor. A counter can monitor any single integer value (for example, a stored procedure that counts how many orders for a particular product have occurred in one day).

Performance information for one particular instance of 'User Settable' object.

Instance name.

As defined by the user.

The Wait Statistics performance object contains performance counters that report information about wait status.

Performance information for one particular instance of 'Wait Statistics' object.

Instance name.

Statistics for processes waiting on a lock.

Statistics for processes waiting for log buffer to be available.

Statistics for processes waiting for log buffer to be written.

Statistics for processes waiting for memory grant to become available.

Statistics relevant to wait on network IO.

Statistics relevant to non-page latches.

Statistics relevant to page IO latches.

Statistics relevant to page latches, not including IO latches

Statistics for processes waiting on thread-safe memory allocators.

Statistics relevant to processes synchronizing access to transaction.

Statistics relevant to processes waiting for worker to become available.

Statistics relevant to processes synchronizing access to workspace.

A table containing performance information for instances of 'Workload Group Stats' objects.

Performance information for one particular instance of 'Workload Group Stats' object.

Instance name.

Number of threads used by parallel queries in the workload group. Serial queries and the main thread of parallel queries are not included in this number.

Number of currently running requests in the workload group.

Number of blocked tasks in the workload group.

System CPU usage by all requests in the specified instance of the performance object.

Maximum CPU time in milliseconds used by a request in the workload group.

Maximum value of memory grant in kilobytes used by a query in the workload group.

Number of query optimizations per second occurring in the workload group.

Number of requests waiting in the queue due to resource governor limits in the workload group.

Number of queries per second getting less than ideal amount of memory in the workload group.

Number of completed requests per second in the workload group.

Number of suboptimal query plans generated per second in the workload group.

This table contains the list of SQL Server Agent instance names installed. The ss2NameIndex is used to refer to all other SQL Server Agent SNMP entries.

Performance information for one SQL Server Agent name instance.

The index number associated with the instance name

The name of the SQL Server Agent installed instance.

The SQL Server Agent Alerts performance object contains performance counters that report information about SQL Server Agent alerts.

Performance information for one particular instance of 'Alerts' object.

The number of Alerts that have activated since the last SQL Server restart.

The number of Alerts that have activated within the last minute.

The SQL Server Agent Jobs performance object contains performance counters that report information about SQL Server Agent jobs.

Performance information for one particular instance of 'Jobs' object.

Instance name.

Number of running jobs.

Number of failed jobs.

Percentage of successful jobs from the total number of executed jobs.

Number of jobs activated within the last minute.

Number of jobs queued.

Number of successful jobs.

The SQL Server Agent JobSteps performance object contains performance counters that report information about SQL Server Agent job steps.

Performance information for one particular instance of 'JobSteps' object.

Instance name.

Number of active steps.

Number of queued steps.

The total number of times any Job Step execution is retried since the last SQL Server restart.

The SQL Server Agent Statistics performance object contains performance counters that report information about SQL Server Agent.

Performance information for one particular instance of 'Statistics' object.

The number of times the SQL Server has been successfully restarted by SQL Server Agent, since the last SQL Server Agent restart.

Number of active sessions.

Number of report server cache hits per second.

Number of times second that models can be retrieved from the cache.

Number of times per second that reports cannot be retrieved from cache.

Number of times second that models cannot be retrieved from the cache.

Number of new user sessions that are started per second.

Number of times per second that reports can be retrieved from the in memory cache.

Number of times per second that reports cannot be retrieved from the in memory cache.

Number of requests per second for reports that are open in an existing session.

Number of active report requests.

Number of reports executed per second.

Number of requests per second.

Total number of report server cache hits.

Total number of cache hits made in the model cache.

Total number of cache misses.

Total number of cache misses made in the model cache.

Total number of cache hits made in the in memory cache.

Total number of cache misses made in the in memory cache.

Total number of processing failures.

Total number of rejected threads as a result of thread pressure.

Total number of reports executed.

Total number of requests being processed.

A table containing performance information for instances of 'MSRS Windows Service' objects.

Performance information for one particular instance of 'MSRS Windows Service' object.

Instance name.

Number of active sessions.

Number of cache flushes per second.

Number of report server cache hits per second.

Number of times second that models can be retrieved from the cache.

Number of times per second that reports cannot be retrieved from cache.

Number of times second that models cannot be retrieved from the cache.

Number of delivers deliveries per second.

Number of events per second.

Number of new user sessions that are started per second.

Number of times per second that reports can be retrieved from the in memory cache.

Number of times per second that reports cannot be retrieved from the in memory cache.

Number of requests per second for reports that are open in an existing session.

Number of active report requests.

Number of reports executed per second.

Number of requests per second.

Number of snapshot updates per second.

Total number of application domain recycles.

Total number of report execution server cache updates.

Total number of report server cache hits.

Total number of cache hits made in the model cache.

Total number of cache misses.