5.0
2021-11-22T02:06:21Z
Templates
App MS SQL Instance Discovery
App MS SQL Instance Discovery
Templates
SQL Server Access Methods
SQL Server Buffer Manager
SQL Server Databases
SQL Server General Statistics
SQL Server Latches
SQL Server Locks
SQL Server Memory Manager
SQL Server SQL Statistics
SQL Services
MSSQL Multi Instance Discovery
windowssqlinstances.discovery
300
{#INSTANCES}
@MSSQL Multi Instance Discovery
A
Discovers multiple SQL Server Instances
{#INSTANCES} Access Methods Forwarded Records/sec
perf_counter["\{#INSTANCES}:Access Methods\Forwarded Records/sec",300]
30
FLOAT
/sec
SQL Server Access Methods
{#INSTANCES} Access Methods Full Scans/sec
perf_counter["\{#INSTANCES}:Access Methods\Full Scans/sec",300]
30
FLOAT
/sec
SQL Server Access Methods
{#INSTANCES} Access Methods Index Searches/sec
perf_counter["\{#INSTANCES}:Access Methods\Index Searches/sec",300]
30
FLOAT
/sec
SQL Server Access Methods
{#INSTANCES} Access Methods Page Splits/sec
perf_counter["\{#INSTANCES}:Access Methods\Page Splits/sec",300]
30
FLOAT
/sec
SQL Server Access Methods
{#INSTANCES} Access Methods Table Lock Escalations
perf_counter["\{#INSTANCES}:Access Methods\Table Lock Escalations/sec",300]
30
FLOAT
SQL Server Access Methods
{#INSTANCES} Buffer Manager Buffer cache hit ratio
perf_counter["\{#INSTANCES}:Buffer Manager\Buffer cache hit ratio",300]
30
FLOAT
SQL Server Buffer Manager
{last()}<90
{#INSTANCES}:Buffer Manager Buffer cache hit ratio
https://msdn.microsoft.com/en-us/ms189628
WARNING
This counter indicates how often SQL Server goes to the buffer, not the hard disk, to get data. The higher this ratio, the less often SQL Server has to go to the hard disk to fetch data, and performance overall is boosted. Unlike many of the other counters available for monitoring SQL Server, this counter averages the Buffer Cache Hit Ratio from the time the last instance of SQL Server was restarted. In other words, this counter is not a real-time measurement, but an average of all the days since SQL Server was last restarted. In OLTP applications, this ratio should exceed 90-95%. If it doesn't, then you need to add more RAM to your server to increase performance. In OLAP applications, the ratio could be much less because of the nature of how OLAP works. In any case, more RAM should increase the performance of SQL Server OLAP activity.
{#INSTANCES} Buffer Manager Free list stalls/sec
perf_counter["\{#INSTANCES}:Buffer Manager\Free list stalls/sec",300]
30
FLOAT
/sec
SQL Server Buffer Manager
{last()}>3
{#INSTANCES}:Buffer Manager Free list stalls/sec
https://msdn.microsoft.com/en-us/ms189628
WARNING
Free list stalls/sec is the frequency with which requests for available database pages are suspended because no buffers are available. Free list stall rates of 3 or 4 per second indicate too little SQL memory available.
{#INSTANCES} Buffer Manager Lazy Writes/sec
perf_counter["\{#INSTANCES}:Buffer Manager\Lazy Writes/sec",300]
30
FLOAT
/sec
SQL Server Buffer Manager
{last()}>20
{#INSTANCES}:Buffer Manager Lazy Writes/Sec
https://msdn.microsoft.com/en-us/ms189628
WARNING
{#INSTANCES} Buffer Manager Page Life Expectancy
perf_counter["\{#INSTANCES}:Buffer Manager\Page Life Expectancy",300]
30
FLOAT
sec
SQL Server Buffer Manager
{last()}<300
{#INSTANCES}:Buffer Manager Page Life Expectancy
https://msdn.microsoft.com/en-us/ms189628
WARNING
{#INSTANCES} Buffer Manager Page lookups/sec
perf_counter["\{#INSTANCES}:Buffer Manager\Page lookups/sec",300]
30
FLOAT
/sec
SQL Server Buffer Manager
{last()}>100
{#INSTANCES}:Buffer Manager Page lookups/sec
https://msdn.microsoft.com/en-us/ms189628
WARNING
Number of requests to find a page in the buffer pool. When the ratio of page lookups to batch requests is much greater than 100, this is an indication that while query plans are looking up data in the buffer pool, these plans are inefficient. Identify queries with the highest amount of logical I/O's and tune them.
{#INSTANCES} Buffer Manager Page reads/sec
perf_counter["\{#INSTANCES}:Buffer Manager\Page reads/sec",300]
30
FLOAT
/sec
SQL Server Buffer Manager
{last()}>90
{#INSTANCES}:Buffer Manager Page reads/sec
https://msdn.microsoft.com/en-us/ms189628
WARNING
Number of physical database page reads issued. 80 – 90 per second is normal, anything that is above indicates indexing or memory constraint.
{#INSTANCES} Buffer Manager Page writes/sec
perf_counter["\{#INSTANCES}:Buffer Manager\Page writes/sec",300]
30
FLOAT
/sec
SQL Server Buffer Manager
{last()}>90
{#INSTANCES}:Buffer Manager Page writes/sec
https://msdn.microsoft.com/en-us/ms189628
WARNING
Number of physical database page reads issued. 80 – 90 per second is normal, anything that is above indicates indexing or memory constraint.
{#INSTANCES} Databases _Total Log Flushes/sec
perf_counter["\{#INSTANCES}:Databases(_Total)\Log Flushes/sec",300]
30
FLOAT
/sec
SQL Server Databases
{#INSTANCES} Databases _Total Transactions/sec
perf_counter["\{#INSTANCES}:Databases(_Total)\Transactions/sec",300]
30
FLOAT
/sec
SQL Server Databases
{#INSTANCES} General Statistics Logins/sec
perf_counter["\{#INSTANCES}:General Statistics\Logins/sec",300]
30
FLOAT
/sec
SQL Server General Statistics
{last()}>2
{#INSTANCES}:General Statistics Logins/sec
https://msdn.microsoft.com/en-us/ms190697
WARNING
> 2 per second indicates that the application is not correctly using connection pooling.
{#INSTANCES} General Statistics Logouts/sec
perf_counter["\{#INSTANCES}:General Statistics\Logouts/sec",300]
30
FLOAT
/sec
SQL Server General Statistics
{last()}>2
{#INSTANCES}:General Statistics Logouts/sec
https://msdn.microsoft.com/en-us/ms190697
WARNING
> 2 per second indicates that the application is not correctly using connection pooling.
{#INSTANCES} General Statistics User Connections
perf_counter["\{#INSTANCES}:General Statistics\User Connections",300]
30
FLOAT
SQL Server General Statistics
{#INSTANCES} Latches Latch Waits/sec
perf_counter["\{#INSTANCES}:Latches\Latch Waits/sec",300]
30
FLOAT
/sec
SQL Server Latches
{#INSTANCES} Latches Total Latch Wait Time (ms)
perf_counter["\{#INSTANCES}:Latches\Total Latch Wait Time (ms)",300]
30
FLOAT
millisec
SQL Server Latches
{last()}>60000
{#INSTANCES}:Latches Total Latch Wait Time (ms)
https://msdn.microsoft.com/en-us/ms190216
WARNING
Total wait time (milliseconds) for locks in the last second. Note: For “Lock Wait Time” it is recommended to look beyond the Avg value. Look for any peaks that are close (or exceeds) to a wait of 60 sec. Though this counter counts how many total milliseconds SQL Server is waiting on locks during the last second, but the counter actually records at the end of locking event. So most probably the peaks represent one huge locking event. If those events exceeds more than 60seconds then they may have extended blocking and could be an issue. In such cases, thoroughly analyze the blocking script output. Some applications are written for timing out after 60 seconds and that’s not acceptable response for those applications.
{#INSTANCES} Locks _Total Lock Waits/sec
perf_counter["\{#INSTANCES}:Locks(_Total)\Lock Waits/sec",300]
30
FLOAT
/sec
SQL Server Locks
{last()}>0
{#INSTANCES}:Locks _Total Lock Waits/sec
https://msdn.microsoft.com/en-us/ms190216
WARNING
This counter reports how many times users waited to acquire a lock over the past second. Note that while you are actually waiting on the lock that this is not reflected in this counter—it gets incremented only when you “wake up” after waiting on the lock. If this value is nonzero then it is an indication that there is at least some level of blocking occurring. If you combine this with the Lock Wait Time counter, you can get some idea of how long the blocking lasted. A zero value for this counter can definitively prove out blocking as a potential cause; a nonzero value will require looking at other information to determine whether it is significant.
{#INSTANCES} Locks _Total Number of Deadlocks/sec
perf_counter["\{#INSTANCES}:Locks(_Total)\Number of Deadlocks/sec",300]
30
FLOAT
/sec
SQL Server Locks
{last()}>1
{#INSTANCES}:Locks_Total Number of Deadlocks/sec
https://msdn.microsoft.com/en-us/ms190216
WARNING
The number of lock requests that resulted in a deadlock.
{#INSTANCES} Memory Manager Total Server Memory (KB)
perf_counter["\{#INSTANCES}:Memory Manager\Total Server Memory (KB)",300]
30
FLOAT
KBytes
SQL Server Memory Manager
{#INSTANCES} SQL Statistics Batch Requests/sec
perf_counter["\{#INSTANCES}:SQL Statistics\Batch Requests/sec",300]
30
FLOAT
/sec
SQL Server SQL Statistics
{#INSTANCES} SQL Statistics SQL Compilations/sec
perf_counter["\{#INSTANCES}:SQL Statistics\SQL Compilations/sec",300]
30
FLOAT
/sec
SQL Server SQL Statistics
{#INSTANCES} SQL Statistics SQL Re-Compilations/sec
perf_counter["\{#INSTANCES}:SQL Statistics\SQL Re-Compilations/sec",300]
30
FLOAT
/sec
SQL Server SQL Statistics
{#INSTANCES} Service
service_state[{#INSTANCES}]
30
FLOAT
SQL Services
Windows service state
{App MS SQL Instance Discovery:perf_counter["\{#INSTANCES}:Access Methods\Forwarded Records/sec",300].last()}>0.1*{App MS SQL Instance Discovery:perf_counter["\{#INSTANCES}:SQL Statistics\Batch Requests/sec",300].last()}
{#INSTANCES}:Access Methods Forwarded Records/sec
https://msdn.microsoft.com/en-us/ms177426
WARNING
{App MS SQL Instance Discovery:perf_counter["\{#INSTANCES}:Access Methods\Index Searches/sec",300].last()}/{App MS SQL Instance Discovery:perf_counter["\{#INSTANCES}:Access Methods\Full Scans/sec",300].last()}>1000
{#INSTANCES}:Access Methods Full Scans/sec
https://msdn.microsoft.com/en-us/ms177426
WARNING
This counter monitors the number of full scans on base tables or indexes. Values greater than 1 or 2 indicate that we are having table / Index page scans. If we see high CPU then we need to investigate this counter, otherwise if the full scans are on small tables we can ignore this counter. A few of the main causes of high Full Scans/sec are • Missing indexes • Too many rows requested Queries with missing indexes or too many rows requested will have a large number of logical reads and an increased CPU time.
{App MS SQL Instance Discovery:perf_counter["\{#INSTANCES}:Access Methods\Page Splits/sec",300].last()}>0.2*{App MS SQL Instance Discovery:perf_counter["\{#INSTANCES}:SQL Statistics\Batch Requests/sec",300].last()}
{#INSTANCES}:Access Methods Page Splits/sec
https://msdn.microsoft.com/en-us/ms177426
WARNING
Number of page splits per second that occur as the result of overflowing index pages. Interesting counter that can lead us to our table / index design. This value needs to be low as possible. If you find out that the number of page splits is high, consider increasing the fillfactor of your indexes. An increased fillfactor helps to reduce page splits because there is more room in data pages before it fills up and a page split has to occur. Note that this counter also includes the new page allocations as well and doesn’t necessarily pose a problem. The other place we can confirm the page splits that involve data or index rows moves are the fragmented indexes on page splits.
{App MS SQL Instance Discovery:perf_counter["\{#INSTANCES}:Latches\Total Latch Wait Time (ms)",300].last()}/{App MS SQL Instance Discovery:perf_counter["\{#INSTANCES}:Latches\Latch Waits/sec",300].last()}>10
{#INSTANCES}:Latches\Latch Waits/sec
https://msdn.microsoft.com/en-us/ms177421
WARNING
{App MS SQL Instance Discovery:perf_counter["\{#INSTANCES}:SQL Statistics\SQL Compilations/sec",300].last()}>0.1*{App MS SQL Instance Discovery:perf_counter["\{#INSTANCES}:SQL Statistics\Batch Requests/sec",300].last()}
{#INSTANCES}:SQL Statistics SQL Compilations/sec
https://msdn.microsoft.com/en-us/ms190911
WARNING
The number of times per second that SQL Server compilations have occurred. This value needs to be as low as possible. If you see a high value such as over 100, then it’s an indication that there are lots of adhoc queries that are running, might cause CPU usage, solution is to re-write these adhoc as stored procedure or use sp_executeSQL.
{App MS SQL Instance Discovery:perf_counter["\{#INSTANCES}:SQL Statistics\SQL Re-Compilations/sec",300].last()}>0.1*{App MS SQL Instance Discovery:perf_counter["\{#INSTANCES}:SQL Statistics\Batch Requests/sec",300].last()}
{#INSTANCES}:SQL Statistics SQL Re-Compilations/sec
https://msdn.microsoft.com/en-us/ms190911
WARNING
The number of times per second that SQL Server recompilations have occurred. This value needs to be as low as possible. If you see a high value such as over 100, then it’s an indication that there are lots of adhoc queries that are running, might cause CPU usage, solution is to re-write these adhoc as stored procedure or use sp_executeSQL.
{#INSTANCES} Access Methods
00C800
-
App MS SQL Instance Discovery
perf_counter["\{#INSTANCES}:Access Methods\Forwarded Records/sec",300]
1
FF3333
-
App MS SQL Instance Discovery
perf_counter["\{#INSTANCES}:Access Methods\Full Scans/sec",300]
2
0000C8
-
App MS SQL Instance Discovery
perf_counter["\{#INSTANCES}:Access Methods\Index Searches/sec",300]
3
C800C8
-
App MS SQL Instance Discovery
perf_counter["\{#INSTANCES}:Access Methods\Page Splits/sec",300]
{#INSTANCES} Buffer Manager
00C800
-
App MS SQL Instance Discovery
perf_counter["\{#INSTANCES}:Buffer Manager\Buffer cache hit ratio",300]
1
FF3333
-
App MS SQL Instance Discovery
perf_counter["\{#INSTANCES}:Buffer Manager\Page Life Expectancy",300]
{#INSTANCES} Buffer Manager Rates
00C800
-
App MS SQL Instance Discovery
perf_counter["\{#INSTANCES}:Buffer Manager\Free list stalls/sec",300]
1
FF3333
-
App MS SQL Instance Discovery
perf_counter["\{#INSTANCES}:Buffer Manager\Lazy Writes/sec",300]
2
0000C8
-
App MS SQL Instance Discovery
perf_counter["\{#INSTANCES}:Buffer Manager\Page lookups/sec",300]
3
C800C8
-
App MS SQL Instance Discovery
perf_counter["\{#INSTANCES}:Buffer Manager\Page reads/sec",300]
4
00C8C8
-
App MS SQL Instance Discovery
perf_counter["\{#INSTANCES}:Buffer Manager\Page writes/sec",300]
{#INSTANCES} Databases _Total
00C800
-
App MS SQL Instance Discovery
perf_counter["\{#INSTANCES}:Databases(_Total)\Log Flushes/sec",300]
1
FF3333
-
App MS SQL Instance Discovery
perf_counter["\{#INSTANCES}:Databases(_Total)\Transactions/sec",300]
{#INSTANCES} Latches and Locks
00C800
-
App MS SQL Instance Discovery
perf_counter["\{#INSTANCES}:Latches\Latch Waits/sec",300]
1
FF3333
-
App MS SQL Instance Discovery
perf_counter["\{#INSTANCES}:Locks(_Total)\Lock Waits/sec",300]
2
0000C8
-
App MS SQL Instance Discovery
perf_counter["\{#INSTANCES}:Locks(_Total)\Number of Deadlocks/sec",300]
{#INSTANCES} SQL Statistics
00C800
-
App MS SQL Instance Discovery
perf_counter["\{#INSTANCES}:SQL Statistics\Batch Requests/sec",300]
1
FF3333
-
App MS SQL Instance Discovery
perf_counter["\{#INSTANCES}:SQL Statistics\SQL Compilations/sec",300]
2
0000C8
-
App MS SQL Instance Discovery
perf_counter["\{#INSTANCES}:SQL Statistics\SQL Re-Compilations/sec",300]
Windows service state
0
Running
1
Paused
2
Start pending
3
Pause pending
4
Continue pending
5
Stop pending
6
Stopped
7
Unknown
255
No such service