Analysis of "SQLDIAG.BLG" Report Generated at: 12/16/2009 4:06:20 PM | PAL

#### On This Page

- Tool Parameters
- Chronological Order

- Alerts by Chronological Order

- Processor

- Processor Utilization Analysis (Alerts: 66)
- Privileged Mode CPU Analysis (Alerts: 6)
- Excessive Processor Use by Processes (Alerts: 23)
- Interrupt Time (Alerts: 0)

- Network

- Network Utilization Analysis (Alerts: 0)
- Network Output Queue Length Analysis (Alerts: 0)
- Memory Committed Bytes (Stats only)

- Disk

- Physical Disk Interface Analysis (Alerts: 0)
- Logical Disk Interface Analysis (Alerts: 0)
- Physical Disk Read Latency Analysis (Alerts: 50)
- Physical Disk Write Latency Analysis (Alerts: 4)
- Logical Disk Read Latency Analysis (Alerts: 51)
- Logical Disk Write Latency Analysis (Alerts: 5)
- Disk Free Space for a Kernel Dump (Alerts: 31)
- Process IO Data Operations/sec (Alerts: 2)
- Process IO Other Operations/sec (Alerts: 1)
- LogicalDisk Disk Transfers/sec (Alerts: 2)

- Memory

- Free System Page Table Entries (Alerts: 0)
- Pool Non Paged Bytes (Alerts: 0)
- Pool Paged Bytes (Alerts: 0)
- Available Memory (Alerts: 31)
- Memory Pages/sec (Alerts: 0)
- Memory Leak Detection (Alerts: 23)
- Handle Leak Detection (Alerts: 0)
- Process Thread Count (Alerts: 0)
- High Virtual Memory Usage (Alerts: 31)
- Process Working Set (Alerts: 0)
- Memory System Cache Resident Bytes (Alerts: 6)
- Memory Pages Input/sec (Alerts: 4)
- Memory Percent Committed Bytes In Use (Alerts: 0)

- SQL Server Process

- Process % Privileged Time (Alerts: 0)

- SQLServer:Access Methods

- SQLServer:Access Methods Forwarded Records/sec (Alerts: 0)
- SQLServer:Access Methods FreeSpace Scans/sec (Alerts: 2)
- SQLServer:Access Methods Full Scans/sec (Alerts: 30)
- SQLServer:Access Methods Page Splits/sec (Alerts: 0)
- SQLServer:Access Methods Scan Point Revalidations/sec (Alerts: 0)
- SQLServer:Access Methods Workfiles Created/sec (Alerts: 1)
- SQLServer:Access Methods Worktables Created/sec (Alerts: 0)
- SQLServer:Access Methods Index Searches/sec (Alerts: 0)

- SQLServer:Buffer Manager

- SQLServer:Buffer Manager Buffer cache hit ratio (Alerts: 0)
- SQLServer:Buffer Manager Free pages (Alerts: 22)
- SQLServer:Buffer Manager Lazy writes/sec (Alerts: 2)
- SQLServer:Buffer Manager Page life expectancy (Alerts: 31)
- SQLServer:Buffer Manager Page lookups/sec (Alerts: 30)
- SQLServer:Buffer Manager Page reads/sec (Alerts: 23)
- SQLServer:Buffer Manager Page writes/sec (Alerts: 1)

- SQLServer:General Statistics

- SQLServer:General Statistics Logins/sec (Stats only)
- SQLServer:General Statistics Logouts/sec (Alerts: 0)
- SQLServer:General Statistics User Connections (Alerts: 3)

- SQLServer:Latches

- SQLServer:Latches Latch Waits/sec (Alerts: 27)
- SQLServer:Latches\Total Latch Wait Time Total Latch Wait Time (ms) (Stats only)

- SQLServer:Memory Manager

- SQLServer:Memory Manager Memory Grants Pending (Alerts: 0)
- SQLServer:Memory Manager Total Server Memory (KB) (Stats only)

- SQLServer:SQL Statistics

- SQLServer:SQL Statistics Batch Requests/sec (Alerts: 0)
- SQLServer:SQL Statistics SQL Compilations/sec (Alerts: 31)
- SQLServer:SQL Statistics SQL Re-Compilations/sec (Alerts: 10)

- SQLServer:Locks

- SQLServer:Locks Lock Requests/sec (Stats only)
- SQLServer:Locks Lock Waits/sec (Stats only)
- SQLServer:Locks Lock Wait Time (ms) (Stats only)
- SQLServer:Locks Number of Deadlocks/sec (Stats only)

- Disclaimer

# Tool Parameters:

Name | Value
--- | ---
Analysis of Log: | SQLDIAG.BLG
Analysis Interval: | 19 second(s)
Threshold File: | SQLServer2005.xml
How many processors (physical and virtual) does the server have? | 2
Was the /3GB switch being used on the server? | False
Was the computer 64-bit? | False
How much memory did the server have in gigabytes? | 2
Is the System set to create a MEMORY.DMP file on C: drive in the event of a server crash (blue screen). By default this is set to C: drive. | True

Back to the top

# Chronological Order

## Alerts by Chronological Order

> Description: This section displays all of the alerts in chronological order.

### Alerts

An alert is generated if any of the thresholds were broken during one of the time intervals analyzed. The background of each of the values represents the highest priority threshold that the value broke. See the each of the counter's respective analysis section for more details about what the threshold means. A white background indicates that the value was not analyzed by any of the thresholds.

Time |  |  |  |  |  |
--- | --- | --- | --- | --- | --- | ---
12/16/2009 1:04:09 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| More than 30% CPU in Privileged Mode CPU - This may indicate a high I/O issue | \\DB04\Processor(1)\% Privileged Time | 19 | 24 | 29 | 0
| More than 30% CPU in Privileged Mode CPU - This may indicate a high I/O issue | \\DB04\Processor(0)\% Privileged Time | 18 | 25 | 29 | 0
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
| This process is using more than 1000 data I/O's per second | \\DB04\Process(wmiprvse)\IO Data Operations/sec | 112 | 1,044 | 1,898 | 0
| This process is using more than 1000 data I/O's per second | \\DB04\Process(lsass)\IO Data Operations/sec | 149 | 1,095 | 1,978 | 0
| This process is using more than 1000 other I/O's per second | \\DB04\Process(lsass)\IO Other Operations/sec | 174 | 1,262 | 2,279 | 0
| Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 41 | 73 | 86 | 0
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| More then 10 page file reads per second | \\DB04\Memory\Pages Input/sec | 116 | 191 | 244 | 0
| > 10% of the number of Batch Requests/Sec | \\DB04\SQLServer:Access Methods\FreeSpace Scans/sec | 0 | 247 | 742 | 0
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 18 | 26 | 34 | 0
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 395 | 12,661 | 32,697 | 0
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.397 | 9.635 | 26.202 | 0
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 1 | 2 | 0
12/16/2009 1:04:28 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| More than 30% CPU in Privileged Mode CPU - This may indicate a high I/O issue | \\DB04\Processor(1)\% Privileged Time | 19 | 25 | 37 | 52
| More than 30% CPU in Privileged Mode CPU - This may indicate a high I/O issue | \\DB04\Processor(0)\% Privileged Time | 25 | 33 | 49 | 1,553
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.007 | 0.027 | 0.084 | 4.218
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.007 | 0.031 | 0.1 | 4.982
| Average disk responsiveness is slow - more than 15ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Write | 0 | 0.013 | 0.046 | 2.447
| Average disk responsiveness is slow - more than 15ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Write | 0 | 0.013 | 0.046 | 2.446
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.007 | 0.027 | 0.084 | 4.219
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0 | 0.302 | 1.201 | 55.937
| Disk responsiveness is very slow (spike of more than 25ms) | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Write | 0 | 0.013 | 0.046 | 2.447
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Write | 0 | 0.224 | 0.891 | 42.495
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
| Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 81 | 100 | 118 | 5,211
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| More then 10 page file reads per second | \\DB04\Memory\Pages Input/sec | 35 | 149 | 259 | -7,949
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 1 | 2 | 3 | 221
| More than 20 Workfiles created per second for every 100 Batch Requests | \\DB04\SQLServer:Access Methods\Workfiles Created/sec | 5 | 13 | 32 | 2,346
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 39 | 47 | 55 | 3,932
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 16,546 | 34,538 | 50,124 | 4,145,035
| Page Writes/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page writes/sec | 0 | 137 | 547 | 25,893
| Possible disparity between User Connections and Batch Requests per second | \\DB04\SQLServer:General Statistics\User Connections | 11 | 12 | 12 | 47.3684210526316
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 25.538 | 60.73 | 110.79 | 9,681.208
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 2 | 4 | 5 | 505
| A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations | \\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec | 0 | 0 | 1 | 69
12/16/2009 1:04:47 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| More than 30% CPU in Privileged Mode CPU - This may indicate a high I/O issue | \\DB04\Processor(1)\% Privileged Time | 11 | 39 | 56 | 1,394
| More than 30% CPU in Privileged Mode CPU - This may indicate a high I/O issue | \\DB04\Processor(0)\% Privileged Time | 17 | 20 | 22 | -481
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0 | 0.072 | 0.21 | 6.419
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0 | 0.093 | 0.272 | 8.392
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0 | 0.072 | 0.21 | 6.419
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(C:)\Avg. Disk sec/Read | 0 | 0.103 | 0.302 | 9.331
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(T:)\Avg. Disk sec/Write | 0 | 0.06 | 0.177 | 5.636
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
| Low on available memory - less than 10% available | \\DB04\Memory\Available MBytes | 117 | 119 | 121 | 4,389
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| More then 10 page file reads per second | \\DB04\Memory\Pages Input/sec | 0 | 9 | 26 | -17,168
| > 10% of the number of Batch Requests/Sec | \\DB04\SQLServer:Access Methods\FreeSpace Scans/sec | 0 | 41 | 115 | -19,511
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 2 | 4 | 8 | 314
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 60 | 65 | 70 | 3,671
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 23,631 | 37,231 | 44,666 | 2,327,696
| Possible disparity between User Connections and Batch Requests per second | \\DB04\SQLServer:General Statistics\User Connections | 11 | 11 | 11 | -47.3684210526316
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 2.78 | 41.721 | 77.923 | 3,039.707
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 2 | 6 | 13 | 477
12/16/2009 1:05:06 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
| Low on available memory - less than 10% available | \\DB04\Memory\Available MBytes | 131 | 131 | 131 | 3,663
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Increasing trend of more than 10MB's per hour detected | \\DB04\Memory\System Cache Resident Bytes | 26,796,032 | 26,846,208 | 26,943,488 | 21,212,968.4210526
| More then 10 page file reads per second | \\DB04\Memory\Pages Input/sec | 0 | 33 | 132 | -9,930
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 1 | 1 | -22
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 75 | 82 | 90 | 3,553
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 0 | 197 | 494 | -787,200
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 0 | 1 | -38
12/16/2009 1:05:25 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
| Low on available memory - less than 10% available | \\DB04\Memory\Available MBytes | 131 | 131 | 131 | 2,747
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Increasing trend of more than 10MB's per hour detected | \\DB04\Memory\System Cache Resident Bytes | 26,357,760 | 26,733,568 | 26,865,664 | 10,574,147.3684211
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 1 | 1 | -19
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 95 | 102 | 110 | 3,612
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 0 | 149 | 294 | -592,692
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 0 | 1 | -26
12/16/2009 1:05:44 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
| Low on available memory - less than 10% available | \\DB04\Memory\Available MBytes | 131 | 131 | 131 | 2,198
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 1 | 1 | -15
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 115 | 123 | 130 | 3,657
| Possible disparity between User Connections and Batch Requests per second | \\DB04\SQLServer:General Statistics\User Connections | 11 | 11 | 11 | -18.9473684210526
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 1 | 5 | 17
12/16/2009 1:06:03 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
| Low on available memory - less than 10% available | \\DB04\Memory\Available MBytes | 131 | 131 | 131 | 1,832
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 1 | 1 | -11
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 135 | 143 | 151 | 3,687
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 0 | 166 | 347 | -394,597
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0 | 0.499 | 1.198 | -288.514
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 0 | 1 | -19
12/16/2009 1:06:22 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
| Low on available memory - less than 10% available | \\DB04\Memory\Available MBytes | 131 | 131 | 131 | 1,570
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 0 | 1 | -18
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 156 | 161 | 166 | 3,647
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2 | 105 | 281 | -339,882
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 0 | 1 | -18
12/16/2009 1:06:41 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| High processor utilization - more than 75% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 21 | 80 | 100 | 559
| High processor utilization - more than 75% CPU utilization | \\DB04\Processor(1)\% Processor Time | 26 | 81 | 100 | 552
| High processor utilization - more than 75% CPU utilization | \\DB04\Processor(0)\% Processor Time | 16 | 79 | 100 | 567
| Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 19 | 139 | 183 | 3,014
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0 | 0.026 | 0.057 | 0.514
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0 | 0.026 | 0.059 | 0.525
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0 | 0.026 | 0.057 | 0.514
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0 | 0.03 | 0.071 | 0.528
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
| Low on available memory - less than 10% available | \\DB04\Memory\Available MBytes | 128 | 129 | 131 | 1,320
| Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,450,659,840 | 1,481,544,704 | 1,493,245,952 | 56,387,368.4210526
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 4 | 15 | 21 | 319
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 171 | 178 | 186 | 3,594
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 8,966 | 91,029 | 139,019 | 1,856,080
| Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 0 | 127 | 257 | 2,506
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 7.181 | 206.715 | 348.054 | 4,667.668
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 8 | 11 | 18 | 237
12/16/2009 1:07:00 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 99 | 99 | 100 | 909
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 98 | 99 | 100 | 871
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 99 | 100 | 100 | 947
| Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 173 | 178 | 181 | 3,494
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0 | 0.15 | 0.529 | 3.07
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0 | 0.15 | 0.529 | 3.074
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0 | 0.15 | 0.529 | 3.07
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0 | 0.151 | 0.529 | 3.032
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
| Less than 80 I/O's per second on average when disk latency is longer than 25ms. This may indicate too many virtual LUNs using the same physical disks on a SAN. This was a spike - not an average. | \\DB04\LogicalDisk(_Total)\Disk Transfers/sec | 9 | 17 | 22 | -2,641
| Less than 80 I/O's per second on average when disk latency is longer than 25ms. This may indicate too many virtual LUNs using the same physical disks on a SAN. This was a spike - not an average. | \\DB04\LogicalDisk(S:)\Disk Transfers/sec | 0 | 5 | 9 | -34
| Low on available memory - less than 10% available | \\DB04\Memory\Available MBytes | 117 | 123 | 128 | 1,047
| Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,492,819,968 | 1,499,601,920 | 1,508,446,208 | 430,274,021.052632
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 12 | 15 | 19 | 293
| Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 36 | 630 | 1,229 | -197,626
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 191 | 198 | 206 | 3,621
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 80,318 | 101,723 | 115,169 | 1,874,984
| Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 2 | 247 | 491 | 4,754
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 175.544 | 227.277 | 288.678 | 4,581.939
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 4 | 8 | 14 | 138
12/16/2009 1:07:19 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 99 | 100 | 100 | 821
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 99 | 100 | 100 | 788
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 99 | 100 | 100 | 854
| Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 178 | 180 | 183 | 3,197
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.032 | 0.05 | 0.061 | 0.875
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.033 | 0.052 | 0.063 | 0.903
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.032 | 0.05 | 0.061 | 0.875
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.035 | 0.052 | 0.063 | 0.853
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
| Low on available memory - less than 10% available | \\DB04\Memory\Available MBytes | 117 | 117 | 117 | 834
| Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,508,077,568 | 1,508,388,864 | 1,508,675,584 | 553,736,084.210526
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Increasing trend of more than 10MB's per hour detected | \\DB04\Memory\System Cache Resident Bytes | 27,045,888 | 27,096,064 | 27,156,480 | 11,098,004.2105263
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 12 | 15 | 18 | 271
| Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 165 | 286 | 417 | -184,372
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 210 | 217 | 221 | 3,614
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 88,460 | 99,527 | 107,960 | 1,645,870
| Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 246 | 247 | 248 | 4,283
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 175.184 | 229.149 | 307.888 | 4,159.201
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 5 | 10 | 15 | 175
12/16/2009 1:07:38 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 100 | 100 | 100 | 747
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 99 | 100 | 100 | 716
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 99 | 100 | 100 | 778
| Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 178 | 184 | 192 | 2,962
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.014 | 0.036 | 0.061 | 0.545
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.018 | 0.038 | 0.061 | 0.573
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.014 | 0.036 | 0.061 | 0.545
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.018 | 0.038 | 0.061 | 0.522
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
| Low on available memory - less than 10% available | \\DB04\Memory\Available MBytes | 117 | 117 | 117 | 758
| Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,508,528,128 | 1,512,427,520 | 1,514,430,464 | 572,961,806.698565
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Increasing trend of more than 10MB's per hour detected | \\DB04\Memory\System Cache Resident Bytes | 27,172,864 | 27,215,189 | 27,254,784 | 12,141,014.354067
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 7 | 9 | 13 | 142
| Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 139 | 186 | 250 | -169,332
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 221 | 221 | 221 | 3,355
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 8,165 | 55,304 | 105,712 | 734,517
| Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 124 | 288 | 495 | 4,612
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 13.127 | 152.942 | 238.86 | 2,468.446
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 3 | 7 | 11 | 97
12/16/2009 1:07:57 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 99 | 100 | 100 | 685
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 98 | 100 | 100 | 655
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 99 | 100 | 100 | 714
| Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 187 | 191 | 195 | 2,835
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.029 | 0.03 | 0.031 | 0.401
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.031 | 0.031 | 0.032 | 0.428
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.029 | 0.03 | 0.031 | 0.401
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.031 | 0.032 | 0.032 | 0.383
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
| Low on available memory - less than 10% available | \\DB04\Memory\Available MBytes | 116 | 116 | 117 | 683
| Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,514,323,968 | 1,514,323,968 | 1,514,323,968 | 555,158,905.263158
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Increasing trend of more than 10MB's per hour detected | \\DB04\Memory\System Cache Resident Bytes | 27,271,168 | 27,334,656 | 27,394,048 | 13,015,578.9473684
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 4 | 8 | 48
| Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 104 | 121 | 127 | -156,257
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 221 | 221 | 221 | 3,075
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,069 | 2,618 | 3,159 | -158,583
| Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 494 | 618 | 743 | 9,435
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.396 | 1.741 | 3.19 | -124.642
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 5 | 10 | 61
12/16/2009 1:08:16 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 100 | 100 | 100 | 634
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 99 | 100 | 100 | 608
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 100 | 100 | 100 | 660
| Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 189 | 190 | 193 | 2,606
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.02 | 0.029 | 0.034 | 0.356
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.021 | 0.03 | 0.036 | 0.38
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.02 | 0.029 | 0.034 | 0.356
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.021 | 0.03 | 0.036 | 0.337
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
| Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 97 | 111 | 116 | 557
| Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,514,323,968 | 1,519,169,536 | 1,533,706,240 | 583,078,037.246964
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Increasing trend of more than 10MB's per hour detected | \\DB04\Memory\System Cache Resident Bytes | 27,426,816 | 27,453,440 | 27,475,968 | 13,745,645.3441296
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 2 | 6 | 21
| Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 111 | 157 | 251 | -143,705
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 59 | 180 | 221 | 2,248
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,150 | 2,427 | 2,809 | -149,170
| Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 603 | 613 | 618 | 8,638
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0 | 0.943 | 2.385 | -126.682
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 3 | 6 | 27
| A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations | \\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec | 0 | 0 | 1 | 2
12/16/2009 1:08:35 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 100 | 100 | 100 | 589
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 100 | 100 | 100 | 566
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 99 | 100 | 100 | 612
| Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 182 | 189 | 192 | 2,394
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.028 | 0.029 | 0.031 | 0.341
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.03 | 0.031 | 0.033 | 0.359
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.028 | 0.029 | 0.031 | 0.341
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.03 | 0.031 | 0.033 | 0.32
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
| Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 93 | 94 | 94 | 281
| Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,629,632 | 1,538,629,632 | 1,538,629,632 | 804,799,326.31579
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 1 | 4 | 8 | 43
| Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 25 | 154 | 241 | -133,488
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 59 | 59 | 59 | 443
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,128 | 2,587 | 3,082 | -136,340
| Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 616 | 617 | 618 | 8,066
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.594 | 1.785 | 3.369 | -106.25
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 5 | 9 | 54
| A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations | \\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec | 0 | 0 | 1 | 3
12/16/2009 1:08:54 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 100 | 100 | 100 | 550
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 100 | 100 | 100 | 529
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 100 | 100 | 100 | 570
| Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 188 | 191 | 194 | 2,266
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.028 | 0.032 | 0.037 | 0.347
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.029 | 0.033 | 0.038 | 0.369
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.028 | 0.032 | 0.037 | 0.347
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.029 | 0.034 | 0.039 | 0.333
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 758 | 776 | -227
| Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 94 | 94 | 94 | 265
| Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,629,632 | 1,538,629,632 | 1,538,629,632 | 751,146,037.894737
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 4 | 8 | 39
| Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 180 | 204 | 237 | -123,954
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 59 | 59 | 59 | 414
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,216 | 2,673 | 3,177 | -126,162
| Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 521 | 587 | 620 | 7,153
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.597 | 1.736 | 3.173 | -99.785
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 5 | 10 | 49
12/16/2009 1:09:13 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 100 | 100 | 100 | 517
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 100 | 100 | 100 | 497
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 100 | 100 | 100 | 537
| Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 185 | 192 | 196 | 2,135
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.03 | 0.031 | 0.032 | 0.315
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.031 | 0.032 | 0.033 | 0.334
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.03 | 0.031 | 0.032 | 0.315
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.031 | 0.033 | 0.033 | 0.299
| Disk responsiveness is very slow (spike of more than 25ms) | \\DB04\LogicalDisk(C:)\Avg. Disk sec/Read | 0 | 0.01 | 0.031 | 0.071
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -853
| Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 94 | 94 | 94 | 249
| Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,629,632 | 1,538,629,632 | 1,538,629,632 | 704,199,410.526316
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 3 | 9 | 21
| Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 140 | 209 | 306 | -116,143
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 44 | 44 | 44 | 210
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,117 | 2,370 | 2,707 | -121,876
| Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 496 | 619 | 743 | 7,088
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.596 | 1.261 | 2.59 | -99.167
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 3 | 10 | 28
12/16/2009 1:09:32 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 99 | 99 | 100 | 481
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 99 | 99 | 100 | 462
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 99 | 99 | 100 | 500
| Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 187 | 190 | 192 | 1,982
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.032 | 0.035 | 0.044 | 0.346
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.034 | 0.037 | 0.047 | 0.369
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.032 | 0.035 | 0.044 | 0.347
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.034 | 0.037 | 0.047 | 0.336
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -802
| Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 93 | 94 | 94 | 231
| Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,629,632 | 1,538,629,632 | 1,538,629,632 | 662,775,915.789474
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 4 | 8 | 35
| Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 147 | 185 | 238 | -109,580
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 44 | 44 | 44 | 198
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,367 | 2,657 | 2,974 | -111,499
| Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 493 | 555 | 739 | 5,955
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 1.188 | 1.686 | 2.575 | -88.597
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 5 | 10 | 43
12/16/2009 1:09:51 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 100 | 100 | 100 | 457
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 99 | 100 | 100 | 439
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 100 | 100 | 100 | 475
| Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 186 | 190 | 197 | 1,873
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.032 | 0.035 | 0.04 | 0.325
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.033 | 0.037 | 0.042 | 0.346
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.032 | 0.035 | 0.04 | 0.325
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.033 | 0.037 | 0.042 | 0.315
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -758
| Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 93 | 93 | 93 | 211
| Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,629,632 | 1,538,629,632 | 1,538,629,632 | 625,955,031.578947
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 1 | 3 | 7 | 23
| Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 123 | 208 | 385 | -103,253
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 44 | 46 | 50 | 208
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,352 | 2,559 | 2,953 | -106,338
| Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 494 | 618 | 740 | 6,290
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.797 | 1.489 | 2.382 | -85.748
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 1 | 4 | 9 | 27
| A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations | \\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec | 0 | 0 | 1 | 2
12/16/2009 1:10:10 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 99 | 100 | 100 | 432
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 99 | 100 | 100 | 416
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 99 | 100 | 100 | 449
| Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 186 | 189 | 191 | 1,773
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.034 | 0.038 | 0.049 | 0.341
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.036 | 0.041 | 0.052 | 0.364
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.034 | 0.038 | 0.049 | 0.341
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.036 | 0.041 | 0.052 | 0.334
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -718
| Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 93 | 93 | 93 | 199
| Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,629,632 | 1,538,629,632 | 1,538,629,632 | 593,010,029.916898
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 3 | 9 | 24
| Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 128 | 177 | 248 | -98,125
| Lazy Writes/second > 20 | \\DB04\SQLServer:Buffer Manager\Lazy writes/sec | 32 | 43 | 56 | 426
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 56 | 64 | 71 | 371
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,124 | 2,590 | 3,059 | -100,439
| Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 496 | 589 | 620 | 5,666
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.199 | 1.194 | 2.188 | -84.178
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 4 | 10 | 33
12/16/2009 1:10:29 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 100 | 100 | 100 | 412
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 100 | 100 | 100 | 398
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 99 | 100 | 100 | 427
| Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 185 | 191 | 194 | 1,695
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.029 | 0.034 | 0.04 | 0.283
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.031 | 0.036 | 0.043 | 0.303
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.029 | 0.034 | 0.04 | 0.283
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.031 | 0.036 | 0.043 | 0.275
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -682
| Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 93 | 93 | 93 | 189
| Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,695,168 | 1,538,695,168 | 1,538,695,168 | 563,980,395.789474
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 6 | 8 | 42
| Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 90 | 180 | 268 | -93,196
| Lazy Writes/second > 20 | \\DB04\SQLServer:Buffer Manager\Lazy writes/sec | 0 | 22 | 65 | 205
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 76 | 79 | 80 | 497
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 1,712 | 2,569 | 3,373 | -95,613
| Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 496 | 579 | 743 | 5,288
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.398 | 1.393 | 2.785 | -78.085
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 7 | 10 | 52
12/16/2009 1:10:48 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 100 | 100 | 100 | 393
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 100 | 100 | 100 | 377
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 99 | 100 | 100 | 408
| Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 186 | 190 | 192 | 1,605
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.03 | 0.033 | 0.036 | 0.256
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.031 | 0.035 | 0.038 | 0.274
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.03 | 0.033 | 0.036 | 0.256
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.031 | 0.036 | 0.039 | 0.256
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -650
| Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 92 | 93 | 95 | 180
| Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,695,168 | 1,538,695,168 | 1,538,695,168 | 537,124,186.466165
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 2 | 8 | 12
| Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 144 | 188 | 231 | -88,687
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 80 | 80 | 80 | 485
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,353 | 2,620 | 2,917 | -90,600
| Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 494 | 618 | 743 | 5,386
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.992 | 1.736 | 2.583 | -71.27
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 3 | 9 | 16
| A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations | \\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec | 0 | 0 | 1 | 1
12/16/2009 1:11:07 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 100 | 100 | 100 | 375
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 99 | 100 | 100 | 360
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 100 | 100 | 100 | 390
| Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 185 | 189 | 193 | 1,528
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.034 | 0.038 | 0.042 | 0.288
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.036 | 0.04 | 0.044 | 0.305
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.034 | 0.038 | 0.042 | 0.288
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.036 | 0.04 | 0.044 | 0.28
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -620
| Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 94 | 94 | 95 | 185
| Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,695,168 | 1,538,695,168 | 1,538,695,168 | 512,709,450.717703
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 1 | 4 | 7 | 27
| Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 160 | 215 | 372 | -84,421
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 80 | 80 | 80 | 463
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,525 | 2,730 | 3,024 | -85,533
| Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 495 | 588 | 742 | 4,888
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 1.195 | 1.989 | 2.583 | -65.853
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 1 | 5 | 9 | 34
| A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations | \\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec | 0 | 0 | 1 | 2
12/16/2009 1:11:26 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 90 | 97 | 100 | 339
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 89 | 97 | 100 | 323
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 91 | 98 | 100 | 355
| Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 172 | 185 | 193 | 1,424
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.029 | 0.08 | 0.23 | 0.626
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.03 | 0.085 | 0.246 | 0.668
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.029 | 0.08 | 0.23 | 0.626
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.03 | 0.085 | 0.246 | 0.644
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -593
| Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 94 | 94 | 94 | 173
| Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,695,168 | 1,538,695,168 | 1,538,695,168 | 490,417,735.469108
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 4 | 9 | 26
| Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 115 | 169 | 255 | -81,130
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 64 | 76 | 80 | 410
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,126 | 2,489 | 3,168 | -83,802
| Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 493 | 556 | 619 | 4,411
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.596 | 1.239 | 2.572 | -69.169
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 5 | 11 | 33
12/16/2009 1:11:45 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 99 | 100 | 100 | 343
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 99 | 100 | 100 | 329
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 99 | 100 | 100 | 356
| Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 182 | 188 | 192 | 1,394
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.032 | 0.037 | 0.043 | 0.255
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.034 | 0.039 | 0.046 | 0.272
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.032 | 0.037 | 0.043 | 0.255
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.034 | 0.039 | 0.046 | 0.249
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -568
| Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 94 | 94 | 94 | 166
| Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,695,168 | 1,538,695,168 | 1,538,695,168 | 469,983,663.157895
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 2 | 6 | 11
| Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 72 | 134 | 203 | -78,022
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 64 | 64 | 64 | 298
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,294 | 2,518 | 2,983 | -80,080
| Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 494 | 588 | 743 | 4,481
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.595 | 1.89 | 3.381 | -61.148
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 3 | 9 | 14
| A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations | \\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec | 0 | 0 | 1 | 1
12/16/2009 1:12:04 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 100 | 100 | 100 | 329
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 100 | 100 | 100 | 317
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 99 | 100 | 100 | 341
| Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 184 | 188 | 192 | 1,340
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.037 | 0.037 | 0.038 | 0.251
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.039 | 0.04 | 0.041 | 0.268
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.037 | 0.037 | 0.038 | 0.251
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.039 | 0.04 | 0.041 | 0.246
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -546
| Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 94 | 94 | 94 | 159
| Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,695,168 | 1,538,695,168 | 1,538,695,168 | 451,184,316.631579
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 1 | 5 | 8 | 32
| Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 163 | 208 | 255 | -74,339
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 64 | 64 | 64 | 286
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,408 | 2,733 | 2,960 | -75,243
| Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 496 | 578 | 743 | 4,227
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.994 | 1.658 | 2.587 | -60.456
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 1 | 6 | 9 | 41
| A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations | \\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec | 0 | 0 | 1 | 2
12/16/2009 1:12:23 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 100 | 100 | 100 | 318
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 100 | 100 | 100 | 306
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 100 | 100 | 100 | 329
| Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 183 | 188 | 192 | 1,288
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.028 | 0.032 | 0.035 | 0.199
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.029 | 0.033 | 0.036 | 0.21
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.028 | 0.032 | 0.035 | 0.199
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.029 | 0.033 | 0.036 | 0.189
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -525
| Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 94 | 94 | 94 | 153
| Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,695,168 | 1,538,695,168 | 1,538,695,168 | 433,831,073.684211
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 2 | 8 | 10
| Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 128 | 166 | 184 | -71,790
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 64 | 64 | 64 | 275
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,139 | 2,560 | 3,214 | -73,613
| Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 494 | 584 | 620 | 4,104
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.596 | 1.638 | 2.388 | -58.279
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 3 | 10 | 13
12/16/2009 1:12:42 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 99 | 100 | 100 | 303
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 99 | 100 | 100 | 291
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 99 | 100 | 100 | 316
| Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 185 | 188 | 190 | 1,241
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.03 | 0.035 | 0.046 | 0.217
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.032 | 0.037 | 0.048 | 0.231
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.03 | 0.035 | 0.046 | 0.217
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.033 | 0.037 | 0.048 | 0.212
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -505
| Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 94 | 95 | 96 | 154
| Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,695,168 | 1,538,695,168 | 1,538,695,168 | 417,763,256.140351
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 4 | 9 | 22
| Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 101 | 227 | 379 | -68,704
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 62 | 62 | 64 | 254
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 1,732 | 2,631 | 3,402 | -70,385
| Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 372 | 557 | 744 | 3,766
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.597 | 1.839 | 3.585 | -54.709
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 5 | 11 | 28
12/16/2009 1:13:01 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 100 | 100 | 100 | 295
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 100 | 100 | 100 | 284
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 100 | 100 | 100 | 306
| Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 185 | 189 | 194 | 1,202
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.03 | 0.036 | 0.043 | 0.211
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.031 | 0.038 | 0.046 | 0.225
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.03 | 0.036 | 0.043 | 0.211
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.032 | 0.038 | 0.046 | 0.207
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -487
| Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 97 | 97 | 97 | 162
| Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,695,168 | 1,538,727,936 | 1,538,826,240 | 403,064,878.195489
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 1 | 4 | 8 | 22
| Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 92 | 178 | 231 | -66,581
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 62 | 62 | 62 | 242
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,351 | 2,737 | 3,060 | -67,158
| Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 495 | 619 | 744 | 4,051
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.398 | 1.888 | 2.982 | -52.423
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 1 | 5 | 9 | 27
| A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations | \\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec | 0 | 0 | 1 | 2
12/16/2009 1:13:20 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 99 | 100 | 100 | 284
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 99 | 100 | 100 | 272
| Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 100 | 100 | 100 | 296
| Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 189 | 194 | 198 | 1,194
| Disk responsiveness is very slow (spike of more than 25ms) | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.002 | 0.012 | 0.03 | 0.047
| Disk responsiveness is very slow (spike of more than 25ms) | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0 | 0.011 | 0.032 | 0.042
| Disk responsiveness is very slow (spike of more than 25ms) | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.002 | 0.012 | 0.03 | 0.047
| Disk responsiveness is very slow (spike of more than 25ms) | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0 | 0.011 | 0.032 | 0.023
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -470
| Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 97 | 99 | 103 | 170
| Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,532,592,128 | 1,536,638,976 | 1,538,695,168 | 375,517,711.796733
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 1 | 3 | 7 | 13
| Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 66 | 198 | 400 | -64,155
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 62 | 62 | 62 | 234
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,457 | 2,715 | 2,888 | -64,984
| Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 0 | 121 | 364 | 657
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.398 | 0.797 | 1.595 | -57.743
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 1 | 4 | 9 | 18
| A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations | \\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec | 0 | 0 | 1 | 1
12/16/2009 1:13:39 PM | Condition | Counter | Min | Avg | Max | Hourly Trend
| Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 67 | 117 | 167 | 666
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.009 | 0.071 | 0.133 | 0.419
| Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.009 | 0.071 | 0.133 | 0.422
| Average disk responsiveness is slow - more than 15ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Write | 0.002 | 0.012 | 0.023 | 0.076
| Average disk responsiveness is slow - more than 15ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Write | 0.002 | 0.012 | 0.023 | 0.076
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.009 | 0.071 | 0.133 | 0.419
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.009 | 0.071 | 0.133 | 0.403
| Disk responsiveness is very slow (spike of more than 25ms) | \\DB04\LogicalDisk(T:)\Avg. Disk sec/Write | 0.003 | 0.015 | 0.027 | 0.091
| Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Write | 0 | 0.027 | 0.055 | 0.171
| Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -455
| Low on available memory - less than 10% available | \\DB04\Memory\Available MBytes | 115 | 115 | 115 | 265
| Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,520,164,864 | 1,522,061,312 | 1,523,957,760 | 270,930,997.894737
| High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
| Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 12 | 17 | 22 | 99
| Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 148 | 182 | 217 | -62,113
| Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 51 | 51 | 51 | 156
| Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 75,778 | 90,860 | 105,942 | 493,887
| Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 1 | 3,755 | 7,509 | 23,584
| Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 234.003 | 1,122.025 | 2,010.048 | 7,025.623
| A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 6 | 11 | 16 | 66

Back to the top

# Processor

## Processor Utilization Analysis

> Description: % Processor Time is the percentage of elapsed time that the processor spends to execute a non-Idle thread. It is calculated by measuring the duration of the idle thread is active in the sample interval, and subtracting that time from interval duration. (Each processor has an idle thread that consumes cycles when no other threads are ready to run). This counter is the primary indicator of processor activity, and displays the average percentage of busy time observed during the sample interval. It is calculated by monitoring the time that the service is inactive, and subtracting that value from 100%. This analysis checks for utilization greater than 60% on each individual processor. If so, determine if it is high user mode CPU or high privileged mode. If high privileged mode CPU is suspected, then see the Privileged Mode CPU Analysis. If a user-mode processor bottleneck is suspected, then consider using a process profiler to analyze the functions causing the high CPU consumption. See “How To: Identify Functions causing a High User-mode CPU Bottleneck for Server Applications in a Production Environment” article in the references section for more information.
> If a user-mode processor bottleneck is suspected, then consider using a process profiler to analyze the functions causing the high CPU consumption. See “How To: Identify Functions causing a High User-mode CPU Bottleneck for Server Applications in a Production Environment” article in the references section for more information.
> References:
> Measuring .NET Application Performance
> http://msdn2.microsoft.com/en-us/library/ms998579.aspx
> How To: Identify Functions causing a High User-mode CPU Bottleneck for Server Applications in a Production Environment http://www.codeplex.com/PerfTesting/Wiki/View.aspx?title=How%20To%3a%20Identify%20a%20Disk%20Performance%20Bottleneck%20Using%20SPA&referringTitle=How%20Tos

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\Processor(_Total)\% Processor Time | 9 | 80 | 100 | 50 | 32 | 87 | 94 | 98
\\DB04\Processor(1)\% Processor Time | 14 | 82 | 100 | 55 | 30 | 88 | 94 | 98
\\DB04\Processor(0)\% Processor Time | 3 | 79 | 100 | 46 | 34 | 86 | 93 | 98

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
12/16/2009 1:06:41 PM | High processor utilization - more than 75% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 21 | 80 | 100 | 559
12/16/2009 1:07:00 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 99 | 99 | 100 | 909
12/16/2009 1:07:19 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 99 | 100 | 100 | 821
12/16/2009 1:07:38 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 100 | 100 | 100 | 747
12/16/2009 1:07:57 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 99 | 100 | 100 | 685
12/16/2009 1:08:16 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 100 | 100 | 100 | 634
12/16/2009 1:08:35 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 100 | 100 | 100 | 589
12/16/2009 1:08:54 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 100 | 100 | 100 | 550
12/16/2009 1:09:13 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 100 | 100 | 100 | 517
12/16/2009 1:09:32 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 99 | 99 | 100 | 481
12/16/2009 1:09:51 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 100 | 100 | 100 | 457
12/16/2009 1:10:10 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 99 | 100 | 100 | 432
12/16/2009 1:10:29 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 100 | 100 | 100 | 412
12/16/2009 1:10:48 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 100 | 100 | 100 | 393
12/16/2009 1:11:07 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 100 | 100 | 100 | 375
12/16/2009 1:11:26 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 90 | 97 | 100 | 339
12/16/2009 1:11:45 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 99 | 100 | 100 | 343
12/16/2009 1:12:04 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 100 | 100 | 100 | 329
12/16/2009 1:12:23 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 100 | 100 | 100 | 318
12/16/2009 1:12:42 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 99 | 100 | 100 | 303
12/16/2009 1:13:01 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 100 | 100 | 100 | 295
12/16/2009 1:13:20 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(_Total)\% Processor Time | 99 | 100 | 100 | 284
12/16/2009 1:06:41 PM | High processor utilization - more than 75% CPU utilization | \\DB04\Processor(1)\% Processor Time | 26 | 81 | 100 | 552
12/16/2009 1:07:00 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 98 | 99 | 100 | 871
12/16/2009 1:07:19 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 99 | 100 | 100 | 788
12/16/2009 1:07:38 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 99 | 100 | 100 | 716
12/16/2009 1:07:57 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 98 | 100 | 100 | 655
12/16/2009 1:08:16 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 99 | 100 | 100 | 608
12/16/2009 1:08:35 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 100 | 100 | 100 | 566
12/16/2009 1:08:54 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 100 | 100 | 100 | 529
12/16/2009 1:09:13 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 100 | 100 | 100 | 497
12/16/2009 1:09:32 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 99 | 99 | 100 | 462
12/16/2009 1:09:51 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 99 | 100 | 100 | 439
12/16/2009 1:10:10 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 99 | 100 | 100 | 416
12/16/2009 1:10:29 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 100 | 100 | 100 | 398
12/16/2009 1:10:48 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 100 | 100 | 100 | 377
12/16/2009 1:11:07 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 99 | 100 | 100 | 360
12/16/2009 1:11:26 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 89 | 97 | 100 | 323
12/16/2009 1:11:45 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 99 | 100 | 100 | 329
12/16/2009 1:12:04 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 100 | 100 | 100 | 317
12/16/2009 1:12:23 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 100 | 100 | 100 | 306
12/16/2009 1:12:42 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 99 | 100 | 100 | 291
12/16/2009 1:13:01 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 100 | 100 | 100 | 284
12/16/2009 1:13:20 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(1)\% Processor Time | 99 | 100 | 100 | 272
12/16/2009 1:06:41 PM | High processor utilization - more than 75% CPU utilization | \\DB04\Processor(0)\% Processor Time | 16 | 79 | 100 | 567
12/16/2009 1:07:00 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 99 | 100 | 100 | 947
12/16/2009 1:07:19 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 99 | 100 | 100 | 854
12/16/2009 1:07:38 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 99 | 100 | 100 | 778
12/16/2009 1:07:57 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 99 | 100 | 100 | 714
12/16/2009 1:08:16 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 100 | 100 | 100 | 660
12/16/2009 1:08:35 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 99 | 100 | 100 | 612
12/16/2009 1:08:54 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 100 | 100 | 100 | 570
12/16/2009 1:09:13 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 100 | 100 | 100 | 537
12/16/2009 1:09:32 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 99 | 99 | 100 | 500
12/16/2009 1:09:51 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 100 | 100 | 100 | 475
12/16/2009 1:10:10 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 99 | 100 | 100 | 449
12/16/2009 1:10:29 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 99 | 100 | 100 | 427
12/16/2009 1:10:48 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 99 | 100 | 100 | 408
12/16/2009 1:11:07 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 100 | 100 | 100 | 390
12/16/2009 1:11:26 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 91 | 98 | 100 | 355
12/16/2009 1:11:45 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 99 | 100 | 100 | 356
12/16/2009 1:12:04 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 99 | 100 | 100 | 341
12/16/2009 1:12:23 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 100 | 100 | 100 | 329
12/16/2009 1:12:42 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 99 | 100 | 100 | 316
12/16/2009 1:13:01 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 100 | 100 | 100 | 306
12/16/2009 1:13:20 PM | Very high processor utilization - more than 90% CPU utilization | \\DB04\Processor(0)\% Processor Time | 100 | 100 | 100 | 296

Back to the top

## Privileged Mode CPU Analysis

> Description: This counter indicates the percentage of time a thread runs in privileged mode. When your application calls operating system functions (for example to perform file or network I/O or to allocate memory), these operating system functions are executed in privileged mode.
> High privileged mode CPU indicates that computer is spending too much time in system I/O versus real (user mode) work. % Privileged Time is the percentage of elapsed time that the process threads spent executing code in privileged mode. When a Windows system service in called, the service will often run in privileged mode to gain access to system-private data. Such data is protected from access by threads executing in user mode. Calls to the system can be explicit or implicit, such as page faults or interrupts. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. Some work done by Windows on behalf of the application might appear in other subsystem processes in addition to the privileged time in the process.
> This analysis checks to see if privileged mode CPU is consuming more than 30% of total CPU. If so, then the CPU consumption is likely caused by another bottleneck other than the processor such as network, memory, or disk I/O.
> References:
> Measuring .NET Application Performance
> http://msdn2.microsoft.com/en-us/library/ms998579.aspx

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\Processor(_Total)\% Privileged Time | 0 | 4 | 38 | -141 | 8 | 3 | 2 | 2
\\DB04\Processor(1)\% Privileged Time | 0 | 4 | 56 | -147 | 9 | 2 | 1 | 1
\\DB04\Processor(0)\% Privileged Time | 0 | 5 | 49 | -135 | 7 | 3 | 3 | 3

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
12/16/2009 1:04:09 PM | More than 30% CPU in Privileged Mode CPU - This may indicate a high I/O issue | \\DB04\Processor(1)\% Privileged Time | 19 | 24 | 29 | 0
12/16/2009 1:04:28 PM | More than 30% CPU in Privileged Mode CPU - This may indicate a high I/O issue | \\DB04\Processor(1)\% Privileged Time | 19 | 25 | 37 | 52
12/16/2009 1:04:47 PM | More than 30% CPU in Privileged Mode CPU - This may indicate a high I/O issue | \\DB04\Processor(1)\% Privileged Time | 11 | 39 | 56 | 1,394
12/16/2009 1:04:09 PM | More than 30% CPU in Privileged Mode CPU - This may indicate a high I/O issue | \\DB04\Processor(0)\% Privileged Time | 18 | 25 | 29 | 0
12/16/2009 1:04:28 PM | More than 30% CPU in Privileged Mode CPU - This may indicate a high I/O issue | \\DB04\Processor(0)\% Privileged Time | 25 | 33 | 49 | 1,553
12/16/2009 1:04:47 PM | More than 30% CPU in Privileged Mode CPU - This may indicate a high I/O issue | \\DB04\Processor(0)\% Privileged Time | 17 | 20 | 22 | -481

Back to the top

## Excessive Processor Use by Processes

> Description: This analysis checks all of the processes to determine if any of the processes are consuming a large amount of CPU.
> If a user-mode processor bottleneck is suspected, then consider using a process profiler to analyze the functions causing the high CPU consumption. See “How To: Identify Functions causing a High User-mode CPU Bottleneck for Server Applications in a Production Environment” article in the references section for more information.
> References:
> Measuring .NET Application Performance
> http://msdn2.microsoft.com/en-us/library/ms998579.aspx
> How To: Identify Functions causing a High User-mode CPU Bottleneck for Server Applications in a Production Environment http://www.codeplex.com/PerfTesting/Wiki/View.aspx?title=How%20To%3a%20Identify%20a%20Disk%20Performance%20Bottleneck%20Using%20SPA&referringTitle=How%20Tos

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\Process(_Total)\% Processor Time | 127 | 190 | 199 | 144 | 6 | 191 | 191 | 192
\\DB04\Process(dfrgifc)\% Processor Time | 0 | 0 | 1 | - | 0 | - | - | -
\\DB04\Process(powershell#4)\% Processor Time | - | - | - | - | - | - | - | -
\\DB04\Process(cmd#4)\% Processor Time | - | - | - | - | - | - | - | -
\\DB04\Process(powershell#3)\% Processor Time | - | - | - | - | - | - | - | -
\\DB04\Process(cmd#3)\% Processor Time | - | - | - | - | - | - | - | -
\\DB04\Process(powershell#2)\% Processor Time | 0 | 2 | 10 | -2 | 1 | 2 | 2 | 2
\\DB04\Process(cmd#2)\% Processor Time | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(SQLCMD#1)\% Processor Time | - | - | - | - | - | - | - | -
\\DB04\Process(SQLCMD)\% Processor Time | 0 | 0 | 1 | -1 | 0 | 0 | 0 | 0
\\DB04\Process(msinfo32)\% Processor Time | 0 | 2 | 8 | -253 | 1 | - | - | -
\\DB04\Process(cmd#1)\% Processor Time | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(SQLdiag)\% Processor Time | 0 | 0 | 1 | -2 | 0 | 0 | 0 | 0
\\DB04\Process(powershell#1)\% Processor Time | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(cmd)\% Processor Time | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(explorer#1)\% Processor Time | 0 | 0 | 1 | -1 | 0 | 0 | - | -
\\DB04\Process(svchost#8)\% Processor Time | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(SQLAGENT)\% Processor Time | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0
\\DB04\Process(fdhost)\% Processor Time | 0 | 0 | 0 | 0 | 0 | - | - | -
\\DB04\Process(sqlservr)\% Processor Time | 0 | 139 | 198 | 666 | 76 | 151 | 167 | 183
\\DB04\Process(Ssms)\% Processor Time | 0 | 1 | 2 | -3 | 0 | 1 | 0 | 0
\\DB04\Process(wpabaln)\% Processor Time | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(powershell)\% Processor Time | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(wmiprvse#1)\% Processor Time | 0 | 0 | 0 | 0 | 0 | - | - | -
\\DB04\Process(explorer)\% Processor Time | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(wmiprvse)\% Processor Time | 0 | 6 | 81 | -339 | 16 | 3 | 0 | 0
\\DB04\Process(alg)\% Processor Time | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(fdlauncher)\% Processor Time | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(svchost#7)\% Processor Time | 0 | 0 | 0 | 0 | 0 | - | - | -
\\DB04\Process(sqlwriter)\% Processor Time | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(svchost#6)\% Processor Time | 0 | 0 | 0 | 0 | 0 | - | - | -
\\DB04\Process(MsDtsSrvr)\% Processor Time | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(svchost#5)\% Processor Time | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(msdtc)\% Processor Time | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(vmicsvc#4)\% Processor Time | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(vmicsvc#3)\% Processor Time | 0 | 0 | 0 | 0 | 0 | 0 | 0 | -
\\DB04\Process(vmicsvc#2)\% Processor Time | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(vmicsvc#1)\% Processor Time | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(vmicsvc)\% Processor Time | 0 | 0 | 0 | -1 | 0 | 0 | 0 | 0
\\DB04\Process(spoolsv)\% Processor Time | 0 | 0 | 0 | 0 | 0 | - | - | -
\\DB04\Process(svchost#4)\% Processor Time | 0 | 1 | 15 | -68 | 2 | 0 | 0 | 0
\\DB04\Process(svchost#3)\% Processor Time | 0 | 0 | 0 | 1 | 0 | 0 | 0 | -
\\DB04\Process(svchost#2)\% Processor Time | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(svchost#1)\% Processor Time | 0 | 0 | 2 | -5 | 0 | 0 | 0 | -
\\DB04\Process(svchost)\% Processor Time | 0 | 0 | 0 | -1 | 0 | - | - | -
\\DB04\Process(lsass)\% Processor Time | 0 | 1 | 14 | -54 | 2 | 0 | 0 | 0
\\DB04\Process(services)\% Processor Time | 0 | 1 | 16 | -11 | 2 | 1 | 1 | 1
\\DB04\Process(winlogon)\% Processor Time | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(csrss)\% Processor Time | 0 | 0 | 3 | -1 | 1 | 0 | 0 | 0
\\DB04\Process(smss)\% Processor Time | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(System)\% Processor Time | 0 | 0 | 3 | -13 | 0 | 0 | 0 | 0
\\DB04\Process(Idle)\% Processor Time | 0 | 39 | 181 | -101 | 65 | 33 | 17 | 8

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\Process(dfrgifc)\% Processor Time | 0 | 0 | 1 | -
* | OK | \\DB04\Process(powershell#4)\% Processor Time | - | - | - | -
* | OK | \\DB04\Process(cmd#4)\% Processor Time | - | - | - | -
* | OK | \\DB04\Process(powershell#3)\% Processor Time | - | - | - | -
* | OK | \\DB04\Process(cmd#3)\% Processor Time | - | - | - | -
* | OK | \\DB04\Process(powershell#2)\% Processor Time | 0 | 2 | 10 | -2
* | OK | \\DB04\Process(cmd#2)\% Processor Time | 0 | - | 0 | 0
* | OK | \\DB04\Process(SQLCMD#1)\% Processor Time | - | - | - | -
* | OK | \\DB04\Process(SQLCMD)\% Processor Time | 0 | 0 | 1 | -1
* | OK | \\DB04\Process(msinfo32)\% Processor Time | 0 | 2 | 8 | -253
* | OK | \\DB04\Process(cmd#1)\% Processor Time | 0 | - | 0 | 0
* | OK | \\DB04\Process(SQLdiag)\% Processor Time | 0 | 0 | 1 | -2
* | OK | \\DB04\Process(powershell#1)\% Processor Time | 0 | - | 0 | 0
* | OK | \\DB04\Process(cmd)\% Processor Time | 0 | - | 0 | 0
* | OK | \\DB04\Process(explorer#1)\% Processor Time | 0 | 0 | 1 | -1
* | OK | \\DB04\Process(svchost#8)\% Processor Time | 0 | - | 0 | 0
* | OK | \\DB04\Process(SQLAGENT)\% Processor Time | 0 | 0 | 1 | 0
* | OK | \\DB04\Process(fdhost)\% Processor Time | 0 | 0 | 0 | 0
12/16/2009 1:06:41 PM | Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 19 | 139 | 183 | 3,014
12/16/2009 1:07:00 PM | Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 173 | 178 | 181 | 3,494
12/16/2009 1:07:19 PM | Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 178 | 180 | 183 | 3,197
12/16/2009 1:07:38 PM | Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 178 | 184 | 192 | 2,962
12/16/2009 1:07:57 PM | Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 187 | 191 | 195 | 2,835
12/16/2009 1:08:16 PM | Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 189 | 190 | 193 | 2,606
12/16/2009 1:08:35 PM | Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 182 | 189 | 192 | 2,394
12/16/2009 1:08:54 PM | Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 188 | 191 | 194 | 2,266
12/16/2009 1:09:13 PM | Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 185 | 192 | 196 | 2,135
12/16/2009 1:09:32 PM | Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 187 | 190 | 192 | 1,982
12/16/2009 1:09:51 PM | Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 186 | 190 | 197 | 1,873
12/16/2009 1:10:10 PM | Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 186 | 189 | 191 | 1,773
12/16/2009 1:10:29 PM | Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 185 | 191 | 194 | 1,695
12/16/2009 1:10:48 PM | Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 186 | 190 | 192 | 1,605
12/16/2009 1:11:07 PM | Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 185 | 189 | 193 | 1,528
12/16/2009 1:11:26 PM | Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 172 | 185 | 193 | 1,424
12/16/2009 1:11:45 PM | Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 182 | 188 | 192 | 1,394
12/16/2009 1:12:04 PM | Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 184 | 188 | 192 | 1,340
12/16/2009 1:12:23 PM | Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 183 | 188 | 192 | 1,288
12/16/2009 1:12:42 PM | Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 185 | 188 | 190 | 1,241
12/16/2009 1:13:01 PM | Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 185 | 189 | 194 | 1,202
12/16/2009 1:13:20 PM | Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 189 | 194 | 198 | 1,194
12/16/2009 1:13:39 PM | Excessive Processor Use Suspected - more than 80% CPU utilization | \\DB04\Process(sqlservr)\% Processor Time | 67 | 117 | 167 | 666

Back to the top

## Interrupt Time

> Description: % Interrupt Time is the time the processor spends receiving and servicing hardware interrupts during sample intervals. This value is an indirect indicator of the activity of devices that generate interrupts, such as the system clock, the mouse, disk drivers, data communication lines, network interface cards and other peripheral devices. These devices normally interrupt the processor when they have completed a task or require attention. Normal thread execution is suspended during interrupts. Most system clocks interrupt the processor every 10 milliseconds, creating a background of interrupt activity. A dramatic increase in this counter indicates potential hardware problems.
> This analysis checks for % Interrupt Time greater than 30%. If this occurs, then consider updating devices drivers for hardware that correlates to this alert.
> References:
> Measuring .NET Application Performance
> http://msdn2.microsoft.com/en-us/library/ms998579.aspx

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\Processor(_Total)\% Interrupt Time | 0 | 0 | 0 | -1 | 0 | 0 | 0 | 0
\\DB04\Processor(1)\% Interrupt Time | 0 | 0 | 0 | -1 | 0 | 0 | 0 | -
\\DB04\Processor(0)\% Interrupt Time | 0 | 0 | 1 | -1 | 0 | 0 | 0 | 0

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\Processor(_Total)\% Interrupt Time | 0 | 0 | 0 | -1
* | OK | \\DB04\Processor(1)\% Interrupt Time | 0 | 0 | 0 | -1
* | OK | \\DB04\Processor(0)\% Interrupt Time | 0 | 0 | 1 | -1

Back to the top

# Network

## Network Utilization Analysis

> Description: Bytes Total/sec is the rate at which bytes are sent and received over each network adapter, including framing characters. Network Interface\Bytes Received/sec is a sum of Network Interface\Bytes Received/sec and Network Interface\Bytes Sent/sec. This counter indicates the rate at which bytes are sent and received over each network adapter. This counter helps you know whether the traffic at your network adapter is saturated and if you need to add another network adapter. How quickly you can identify a problem depends on the type of network you have as well as whether you share bandwidth with other applications.
> This analysis converts Bytes Total/sec to bits and compares it to the current bandwidth of the network adapter to calculate network utilization. Next, it checks for utilization above 50%.
> Reference:
> Measuring .NET Application Performance
> http://msdn2.microsoft.com/en-us/library/ms998579.aspx

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\Network Interface(MS TCP Loopback interface)\Bytes Total/sec | 0 | 11 | 65 | -131 | 9 | 11 | 11 | 13
\\DB04\Network Interface(Microsoft Virtual Machine Bus Network Adapter)\Bytes Total/sec | 0 | 31,836 | 745,864 | 64,277 | 47,435 | 25,432 | 26,813 | 27,873

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\Network Interface(MS TCP Loopback interface)\Bytes Total/sec | 0 | 11 | 65 | -131
* | OK | \\DB04\Network Interface(Microsoft Virtual Machine Bus Network Adapter)\Bytes Total/sec | 0 | 31,836 | 745,864 | 64,277

Back to the top

## Network Output Queue Length Analysis

> Description: This analysis checks to see how many threads are waiting on the network adapter. If there are a lot of threads waiting on the network adapter, then the system is most likely saturating the network I/O most likely due to network latency or network bandwidth.
> Output Queue Length is the length of the output packet queue (in packets). If this is longer than two, there are delays and the bottleneck should be found and eliminated, if possible. Since the requests are queued by the Network Driver Interface Specification (NDIS) in this implementation, this will always be 0.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\Network Interface(MS TCP Loopback interface)\Output Queue Length | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Network Interface(Microsoft Virtual Machine Bus Network Adapter)\Output Queue Length | 0 | - | 0 | 0 | 0 | - | - | -

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\Network Interface(MS TCP Loopback interface)\Output Queue Length | 0 | - | 0 | 0
* | OK | \\DB04\Network Interface(Microsoft Virtual Machine Bus Network Adapter)\Output Queue Length | 0 | - | 0 | 0

Back to the top

## Memory Committed Bytes

> Description: Committed Bytes is the amount of committed virtual memory, in bytes. Committed memory is the physical memory which has space reserved on the disk paging file(s). There can be one or more paging files on each physical drive. This counter displays the last observed value only; it is not an average.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\Memory\Committed Bytes | 2,150,879,232 | 2,219,603,902 | 2,309,332,992 | -24,136,219 | 35,119,330 | 2,225,144,753 | 2,231,806,447 | 2,236,579,840

Back to the top

# Disk

## Physical Disk Interface Analysis

> Description: This analysis analyzes the idle time of each of the physical disks. The more idle the disk, the less the disk is being used. This counter is best used to determine if there is a bottleneck in the disk interface such as SAN fabric or SCSI controller.
> % Idle Time reports the percentage of time during the sample interval that the disk was idle.
> Reference:
> Ruling Out Disk-Bound Problems
> http://technet.microsoft.com/en-us/library/5bcdd349-dcc6-43eb-9dc3-54175f7061ad.aspx

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\PhysicalDisk(_Total)\% Idle Time | 59 | 96 | 100 | -37 | 4 | 97 | 97 | 97
\\DB04\PhysicalDisk(1 P:)\% Idle Time | 99 | 100 | 101 | 1 | 0 | 100 | 100 | 100
\\DB04\PhysicalDisk(0 C: S: T:)\% Idle Time | 18 | 92 | 100 | -76 | 9 | 94 | 93 | 93

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\PhysicalDisk(_Total)\% Idle Time | 59 | 96 | 100 | -37
* | OK | \\DB04\PhysicalDisk(1 P:)\% Idle Time | 99 | 100 | 101 | 1
* | OK | \\DB04\PhysicalDisk(0 C: S: T:)\% Idle Time | 18 | 92 | 100 | -76

Back to the top

## Logical Disk Interface Analysis

> Description: This analysis analyzes the idle time of each of the physical disks. The more idle the disk, the less the disk is being used. This counter is best used to determine if there is a bottleneck in the disk interface such as SAN fabric or SCSI controller.
> % Idle Time reports the percentage of time during the sample interval that the disk was idle.
> Reference:
> Ruling Out Disk-Bound Problems
> http://technet.microsoft.com/en-us/library/5bcdd349-dcc6-43eb-9dc3-54175f7061ad.aspx

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\LogicalDisk(_Total)\% Idle Time | 75 | 98 | 100 | -30 | 3 | 99 | 99 | 99
\\DB04\LogicalDisk(P:)\% Idle Time | 99 | 100 | 101 | 1 | 0 | 100 | 100 | 100
\\DB04\LogicalDisk(T:)\% Idle Time | 86 | 100 | 101 | -32 | 1 | 100 | 100 | 100
\\DB04\LogicalDisk(S:)\% Idle Time | 19 | 94 | 101 | -240 | 7 | 96 | 95 | 95
\\DB04\LogicalDisk(C:)\% Idle Time | 50 | 97 | 100 | 153 | 6 | 99 | 99 | 99

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\LogicalDisk(_Total)\% Idle Time | 75 | 98 | 100 | -30
* | OK | \\DB04\LogicalDisk(P:)\% Idle Time | 99 | 100 | 101 | 1
* | OK | \\DB04\LogicalDisk(T:)\% Idle Time | 86 | 100 | 101 | -32
* | OK | \\DB04\LogicalDisk(S:)\% Idle Time | 19 | 94 | 101 | -240
* | OK | \\DB04\LogicalDisk(C:)\% Idle Time | 50 | 97 | 100 | 153

Back to the top

## Physical Disk Read Latency Analysis

> Description: Avg. Disk sec/Read is the average time, in seconds, of a read of data to the disk. This analysis determines if any of the physical disks are responding slowly.
> If the response times are greater than .015 (15 milliseconds), then the disk subsystem is keeping up with demand, but does not have much overhead left.
> If the response times are greater than .025 (25 milliseconds), then noticeable slow downs and performance issues affecting users may be occurring.
> Reference:
> Ruling Out Disk-Bound Problems
> http://technet.microsoft.com/en-us/library/5bcdd349-dcc6-43eb-9dc3-54175f7061ad.aspx

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0 | 0.035 | 0.529 | 0.419 | 0.029 | 0.032 | 0.032 | 0.033
\\DB04\PhysicalDisk(1 P:)\Avg. Disk sec/Read | 0 | 0.002 | 0.007 | 0.007 | 0.001 | 0.002 | 0.002 | 0.003
\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0 | 0.037 | 0.529 | 0.422 | 0.03 | 0.034 | 0.034 | 0.035

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
12/16/2009 1:04:28 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.007 | 0.027 | 0.084 | 4.218
12/16/2009 1:04:47 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0 | 0.072 | 0.21 | 6.419
12/16/2009 1:06:41 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0 | 0.026 | 0.057 | 0.514
12/16/2009 1:07:00 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0 | 0.15 | 0.529 | 3.07
12/16/2009 1:07:19 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.032 | 0.05 | 0.061 | 0.875
12/16/2009 1:07:38 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.014 | 0.036 | 0.061 | 0.545
12/16/2009 1:07:57 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.029 | 0.03 | 0.031 | 0.401
12/16/2009 1:08:16 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.02 | 0.029 | 0.034 | 0.356
12/16/2009 1:08:35 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.028 | 0.029 | 0.031 | 0.341
12/16/2009 1:08:54 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.028 | 0.032 | 0.037 | 0.347
12/16/2009 1:09:13 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.03 | 0.031 | 0.032 | 0.315
12/16/2009 1:09:32 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.032 | 0.035 | 0.044 | 0.346
12/16/2009 1:09:51 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.032 | 0.035 | 0.04 | 0.325
12/16/2009 1:10:10 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.034 | 0.038 | 0.049 | 0.341
12/16/2009 1:10:29 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.029 | 0.034 | 0.04 | 0.283
12/16/2009 1:10:48 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.03 | 0.033 | 0.036 | 0.256
12/16/2009 1:11:07 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.034 | 0.038 | 0.042 | 0.288
12/16/2009 1:11:26 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.029 | 0.08 | 0.23 | 0.626
12/16/2009 1:11:45 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.032 | 0.037 | 0.043 | 0.255
12/16/2009 1:12:04 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.037 | 0.037 | 0.038 | 0.251
12/16/2009 1:12:23 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.028 | 0.032 | 0.035 | 0.199
12/16/2009 1:12:42 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.03 | 0.035 | 0.046 | 0.217
12/16/2009 1:13:01 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.03 | 0.036 | 0.043 | 0.211
12/16/2009 1:13:20 PM | Disk responsiveness is very slow (spike of more than 25ms) | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.002 | 0.012 | 0.03 | 0.047
12/16/2009 1:13:39 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Read | 0.009 | 0.071 | 0.133 | 0.419
12/16/2009 1:04:28 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.007 | 0.031 | 0.1 | 4.982
12/16/2009 1:04:47 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0 | 0.093 | 0.272 | 8.392
12/16/2009 1:06:41 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0 | 0.026 | 0.059 | 0.525
12/16/2009 1:07:00 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0 | 0.15 | 0.529 | 3.074
12/16/2009 1:07:19 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.033 | 0.052 | 0.063 | 0.903
12/16/2009 1:07:38 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.018 | 0.038 | 0.061 | 0.573
12/16/2009 1:07:57 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.031 | 0.031 | 0.032 | 0.428
12/16/2009 1:08:16 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.021 | 0.03 | 0.036 | 0.38
12/16/2009 1:08:35 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.03 | 0.031 | 0.033 | 0.359
12/16/2009 1:08:54 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.029 | 0.033 | 0.038 | 0.369
12/16/2009 1:09:13 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.031 | 0.032 | 0.033 | 0.334
12/16/2009 1:09:32 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.034 | 0.037 | 0.047 | 0.369
12/16/2009 1:09:51 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.033 | 0.037 | 0.042 | 0.346
12/16/2009 1:10:10 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.036 | 0.041 | 0.052 | 0.364
12/16/2009 1:10:29 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.031 | 0.036 | 0.043 | 0.303
12/16/2009 1:10:48 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.031 | 0.035 | 0.038 | 0.274
12/16/2009 1:11:07 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.036 | 0.04 | 0.044 | 0.305
12/16/2009 1:11:26 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.03 | 0.085 | 0.246 | 0.668
12/16/2009 1:11:45 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.034 | 0.039 | 0.046 | 0.272
12/16/2009 1:12:04 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.039 | 0.04 | 0.041 | 0.268
12/16/2009 1:12:23 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.029 | 0.033 | 0.036 | 0.21
12/16/2009 1:12:42 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.032 | 0.037 | 0.048 | 0.231
12/16/2009 1:13:01 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.031 | 0.038 | 0.046 | 0.225
12/16/2009 1:13:20 PM | Disk responsiveness is very slow (spike of more than 25ms) | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0 | 0.011 | 0.032 | 0.042
12/16/2009 1:13:39 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Read | 0.009 | 0.071 | 0.133 | 0.422

Back to the top

## Physical Disk Write Latency Analysis

> Description: Avg. Disk sec/Write is the average time, in seconds, of a write of data to the disk. This analysis determines if any of the physical disks are responding slowly.
> If the response times are greater than .015 (15 milliseconds), then the disk subsystem is keeping up with demand, but does not have much overhead left.
> If the response times are greater than .025 (25 milliseconds), then noticeable slow downs and performance issues affecting users may be occurring.
> Reference:
> Ruling Out Disk-Bound Problems
> http://technet.microsoft.com/en-us/library/5bcdd349-dcc6-43eb-9dc3-54175f7061ad.aspx

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Write | 0 | 0.002 | 0.046 | 0.076 | 0.003 | 0.002 | 0.002 | 0.002
\\DB04\PhysicalDisk(1 P:)\Avg. Disk sec/Write | 0 | 0 | 0 | -0.001 | 0 | - | - | -
\\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Write | 0 | 0.002 | 0.046 | 0.076 | 0.003 | 0.002 | 0.002 | 0.002

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
12/16/2009 1:04:28 PM | Average disk responsiveness is slow - more than 15ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Write | 0 | 0.013 | 0.046 | 2.447
12/16/2009 1:13:39 PM | Average disk responsiveness is slow - more than 15ms | \\DB04\PhysicalDisk(_Total)\Avg. Disk sec/Write | 0.002 | 0.012 | 0.023 | 0.076
12/16/2009 1:04:28 PM | Average disk responsiveness is slow - more than 15ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Write | 0 | 0.013 | 0.046 | 2.446
12/16/2009 1:13:39 PM | Average disk responsiveness is slow - more than 15ms | \\DB04\PhysicalDisk(0 C: S: T:)\Avg. Disk sec/Write | 0.002 | 0.012 | 0.023 | 0.076

Back to the top

## Logical Disk Read Latency Analysis

> Description: Avg. Disk sec/Read is the average time, in seconds, of a read of data to the disk. This analysis determines if any of the physical disks are responding slowly.
> If the response times are greater than .015 (15 milliseconds), then the disk subsystem is keeping up with demand, but does not have much overhead left.
> If the response times are greater than .025 (25 milliseconds), then noticeable slow downs and performance issues affecting users may be occurring.
> Reference:
> Ruling Out Disk-Bound Problems
> http://technet.microsoft.com/en-us/library/5bcdd349-dcc6-43eb-9dc3-54175f7061ad.aspx

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0 | 0.035 | 0.529 | 0.419 | 0.029 | 0.032 | 0.032 | 0.033
\\DB04\LogicalDisk(P:)\Avg. Disk sec/Read | 0 | 0.002 | 0.007 | 0.007 | 0.001 | 0.002 | 0.002 | 0.003
\\DB04\LogicalDisk(T:)\Avg. Disk sec/Read | 0 | 0 | 0.012 | -0.026 | 0.001 | - | - | -
\\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0 | 0.043 | 1.201 | 0.403 | 0.056 | 0.033 | 0.033 | 0.035
\\DB04\LogicalDisk(C:)\Avg. Disk sec/Read | 0 | 0.005 | 0.302 | -0.028 | 0.018 | 0.002 | 0.001 | 0.001

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
12/16/2009 1:04:28 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.007 | 0.027 | 0.084 | 4.219
12/16/2009 1:04:47 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0 | 0.072 | 0.21 | 6.419
12/16/2009 1:06:41 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0 | 0.026 | 0.057 | 0.514
12/16/2009 1:07:00 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0 | 0.15 | 0.529 | 3.07
12/16/2009 1:07:19 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.032 | 0.05 | 0.061 | 0.875
12/16/2009 1:07:38 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.014 | 0.036 | 0.061 | 0.545
12/16/2009 1:07:57 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.029 | 0.03 | 0.031 | 0.401
12/16/2009 1:08:16 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.02 | 0.029 | 0.034 | 0.356
12/16/2009 1:08:35 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.028 | 0.029 | 0.031 | 0.341
12/16/2009 1:08:54 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.028 | 0.032 | 0.037 | 0.347
12/16/2009 1:09:13 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.03 | 0.031 | 0.032 | 0.315
12/16/2009 1:09:32 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.032 | 0.035 | 0.044 | 0.347
12/16/2009 1:09:51 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.032 | 0.035 | 0.04 | 0.325
12/16/2009 1:10:10 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.034 | 0.038 | 0.049 | 0.341
12/16/2009 1:10:29 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.029 | 0.034 | 0.04 | 0.283
12/16/2009 1:10:48 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.03 | 0.033 | 0.036 | 0.256
12/16/2009 1:11:07 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.034 | 0.038 | 0.042 | 0.288
12/16/2009 1:11:26 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.029 | 0.08 | 0.23 | 0.626
12/16/2009 1:11:45 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.032 | 0.037 | 0.043 | 0.255
12/16/2009 1:12:04 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.037 | 0.037 | 0.038 | 0.251
12/16/2009 1:12:23 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.028 | 0.032 | 0.035 | 0.199
12/16/2009 1:12:42 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.03 | 0.035 | 0.046 | 0.217
12/16/2009 1:13:01 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.03 | 0.036 | 0.043 | 0.211
12/16/2009 1:13:20 PM | Disk responsiveness is very slow (spike of more than 25ms) | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.002 | 0.012 | 0.03 | 0.047
12/16/2009 1:13:39 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Read | 0.009 | 0.071 | 0.133 | 0.419
12/16/2009 1:04:28 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0 | 0.302 | 1.201 | 55.937
12/16/2009 1:06:41 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0 | 0.03 | 0.071 | 0.528
12/16/2009 1:07:00 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0 | 0.151 | 0.529 | 3.032
12/16/2009 1:07:19 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.035 | 0.052 | 0.063 | 0.853
12/16/2009 1:07:38 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.018 | 0.038 | 0.061 | 0.522
12/16/2009 1:07:57 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.031 | 0.032 | 0.032 | 0.383
12/16/2009 1:08:16 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.021 | 0.03 | 0.036 | 0.337
12/16/2009 1:08:35 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.03 | 0.031 | 0.033 | 0.32
12/16/2009 1:08:54 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.029 | 0.034 | 0.039 | 0.333
12/16/2009 1:09:13 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.031 | 0.033 | 0.033 | 0.299
12/16/2009 1:09:32 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.034 | 0.037 | 0.047 | 0.336
12/16/2009 1:09:51 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.033 | 0.037 | 0.042 | 0.315
12/16/2009 1:10:10 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.036 | 0.041 | 0.052 | 0.334
12/16/2009 1:10:29 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.031 | 0.036 | 0.043 | 0.275
12/16/2009 1:10:48 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.031 | 0.036 | 0.039 | 0.256
12/16/2009 1:11:07 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.036 | 0.04 | 0.044 | 0.28
12/16/2009 1:11:26 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.03 | 0.085 | 0.246 | 0.644
12/16/2009 1:11:45 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.034 | 0.039 | 0.046 | 0.249
12/16/2009 1:12:04 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.039 | 0.04 | 0.041 | 0.246
12/16/2009 1:12:23 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.029 | 0.033 | 0.036 | 0.189
12/16/2009 1:12:42 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.033 | 0.037 | 0.048 | 0.212
12/16/2009 1:13:01 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.032 | 0.038 | 0.046 | 0.207
12/16/2009 1:13:20 PM | Disk responsiveness is very slow (spike of more than 25ms) | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0 | 0.011 | 0.032 | 0.023
12/16/2009 1:13:39 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Read | 0.009 | 0.071 | 0.133 | 0.403
12/16/2009 1:04:47 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(C:)\Avg. Disk sec/Read | 0 | 0.103 | 0.302 | 9.331
12/16/2009 1:09:13 PM | Disk responsiveness is very slow (spike of more than 25ms) | \\DB04\LogicalDisk(C:)\Avg. Disk sec/Read | 0 | 0.01 | 0.031 | 0.071

Back to the top

## Logical Disk Write Latency Analysis

> Description: Avg. Disk sec/Write is the average time, in seconds, of a write of data to the disk. This analysis determines if any of the physical disks are responding slowly.
> If the response times are greater than .015 (15 milliseconds), then the disk subsystem is keeping up with demand, but does not have much overhead left.
> If the response times are greater than .025 (25 milliseconds), then noticeable slow downs and performance issues affecting users may be occurring.
> Reference:
> Ruling Out Disk-Bound Problems
> http://technet.microsoft.com/en-us/library/5bcdd349-dcc6-43eb-9dc3-54175f7061ad.aspx

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\LogicalDisk(_Total)\Avg. Disk sec/Write | 0 | 0.002 | 0.046 | 0.076 | 0.003 | 0.002 | 0.002 | 0.002
\\DB04\LogicalDisk(P:)\Avg. Disk sec/Write | 0 | 0 | 0 | -0.001 | 0 | - | - | -
\\DB04\LogicalDisk(T:)\Avg. Disk sec/Write | 0 | 0.004 | 0.177 | 0.091 | 0.01 | 0.002 | 0.002 | 0.002
\\DB04\LogicalDisk(S:)\Avg. Disk sec/Write | 0 | 0.009 | 0.891 | 0.171 | 0.04 | 0.001 | 0.001 | 0.001
\\DB04\LogicalDisk(C:)\Avg. Disk sec/Write | 0 | 0.002 | 0.021 | 0.033 | 0.001 | 0.001 | 0.001 | 0.001

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
12/16/2009 1:04:28 PM | Disk responsiveness is very slow (spike of more than 25ms) | \\DB04\LogicalDisk(_Total)\Avg. Disk sec/Write | 0 | 0.013 | 0.046 | 2.447
12/16/2009 1:04:47 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(T:)\Avg. Disk sec/Write | 0 | 0.06 | 0.177 | 5.636
12/16/2009 1:13:39 PM | Disk responsiveness is very slow (spike of more than 25ms) | \\DB04\LogicalDisk(T:)\Avg. Disk sec/Write | 0.003 | 0.015 | 0.027 | 0.091
12/16/2009 1:04:28 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Write | 0 | 0.224 | 0.891 | 42.495
12/16/2009 1:13:39 PM | Average disk responsiveness is very slow - more than 25ms | \\DB04\LogicalDisk(S:)\Avg. Disk sec/Write | 0 | 0.027 | 0.055 | 0.171

Back to the top

## Disk Free Space for a Kernel Dump

> Description: The default setting of complete memory dumps (blue screens) is to purge all of the physical memory to the C: drive under the windows directory as a memory.dmp file. This analysis checks to make sure there is enough free disk space for the operating system to dump all memory to disk.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 741 | 776 | -455 | 36 | 742 | 743 | 744

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
12/16/2009 1:04:09 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
12/16/2009 1:04:28 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
12/16/2009 1:04:47 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
12/16/2009 1:05:06 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
12/16/2009 1:05:25 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
12/16/2009 1:05:44 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
12/16/2009 1:06:03 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
12/16/2009 1:06:22 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
12/16/2009 1:06:41 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
12/16/2009 1:07:00 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
12/16/2009 1:07:19 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
12/16/2009 1:07:38 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
12/16/2009 1:07:57 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
12/16/2009 1:08:16 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
12/16/2009 1:08:35 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 776 | 776 | 776 | 0
12/16/2009 1:08:54 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 758 | 776 | -227
12/16/2009 1:09:13 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -853
12/16/2009 1:09:32 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -802
12/16/2009 1:09:51 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -758
12/16/2009 1:10:10 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -718
12/16/2009 1:10:29 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -682
12/16/2009 1:10:48 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -650
12/16/2009 1:11:07 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -620
12/16/2009 1:11:26 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -593
12/16/2009 1:11:45 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -568
12/16/2009 1:12:04 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -546
12/16/2009 1:12:23 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -525
12/16/2009 1:12:42 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -505
12/16/2009 1:13:01 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -487
12/16/2009 1:13:20 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -470
12/16/2009 1:13:39 PM | Not enough disk space on C: drive for a kernel dump (blue screen) | \\DB04\LogicalDisk(C:)\Free Megabytes | 704 | 704 | 704 | -455

Back to the top

## Process IO Data Operations/sec

> Description: The rate at which the process is issuing read and write I/O operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\Process(_Total)\IO Data Operations/sec | 5 | 180 | 3,908 | -12,892 | 457 | 66 | 56 | 55
\\DB04\Process(dfrgifc)\IO Data Operations/sec | 0 | 2 | 3 | - | 0 | - | - | -
\\DB04\Process(powershell#4)\IO Data Operations/sec | - | - | - | - | - | - | - | -
\\DB04\Process(cmd#4)\IO Data Operations/sec | - | - | - | - | - | - | - | -
\\DB04\Process(powershell#3)\IO Data Operations/sec | - | - | - | - | - | - | - | -
\\DB04\Process(cmd#3)\IO Data Operations/sec | - | - | - | - | - | - | - | -
\\DB04\Process(powershell#2)\IO Data Operations/sec | 0 | 0 | 1 | 3 | 0 | 0 | 0 | 0
\\DB04\Process(cmd#2)\IO Data Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(SQLCMD#1)\IO Data Operations/sec | - | - | - | - | - | - | - | -
\\DB04\Process(SQLCMD)\IO Data Operations/sec | 0 | 13 | 147 | 39 | 16 | 12 | 10 | 5
\\DB04\Process(msinfo32)\IO Data Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(cmd#1)\IO Data Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(SQLdiag)\IO Data Operations/sec | 0 | 1 | 2 | -3 | 0 | 1 | 1 | 1
\\DB04\Process(powershell#1)\IO Data Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(cmd)\IO Data Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(explorer#1)\IO Data Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(svchost#8)\IO Data Operations/sec | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0
\\DB04\Process(SQLAGENT)\IO Data Operations/sec | 0 | 1 | 2 | 0 | 0 | 1 | 1 | 1
\\DB04\Process(fdhost)\IO Data Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(sqlservr)\IO Data Operations/sec | 0 | 21 | 350 | 410 | 20 | 19 | 17 | 18
\\DB04\Process(Ssms)\IO Data Operations/sec | 0 | 1 | 2 | 2 | 0 | 1 | 1 | 1
\\DB04\Process(wpabaln)\IO Data Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(powershell)\IO Data Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(wmiprvse#1)\IO Data Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(explorer)\IO Data Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(wmiprvse)\IO Data Operations/sec | 0 | 61 | 1,898 | -6,587 | 221 | 5 | 1 | 1
\\DB04\Process(alg)\IO Data Operations/sec | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0
\\DB04\Process(fdlauncher)\IO Data Operations/sec | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0
\\DB04\Process(svchost#7)\IO Data Operations/sec | 0 | 0 | 2 | 0 | 0 | 0 | 0 | 0
\\DB04\Process(sqlwriter)\IO Data Operations/sec | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0
\\DB04\Process(svchost#6)\IO Data Operations/sec | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0
\\DB04\Process(MsDtsSrvr)\IO Data Operations/sec | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0
\\DB04\Process(svchost#5)\IO Data Operations/sec | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0
\\DB04\Process(msdtc)\IO Data Operations/sec | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0
\\DB04\Process(vmicsvc#4)\IO Data Operations/sec | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0
\\DB04\Process(vmicsvc#3)\IO Data Operations/sec | 1 | 1 | 1 | 0 | 0 | 1 | 1 | 1
\\DB04\Process(vmicsvc#2)\IO Data Operations/sec | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0
\\DB04\Process(vmicsvc#1)\IO Data Operations/sec | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0
\\DB04\Process(vmicsvc)\IO Data Operations/sec | 1 | 1 | 2 | 1 | 0 | 1 | 1 | 1
\\DB04\Process(spoolsv)\IO Data Operations/sec | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0
\\DB04\Process(svchost#4)\IO Data Operations/sec | 2 | 8 | 98 | -225 | 6 | 7 | 7 | 7
\\DB04\Process(svchost#3)\IO Data Operations/sec | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0
\\DB04\Process(svchost#2)\IO Data Operations/sec | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0
\\DB04\Process(svchost#1)\IO Data Operations/sec | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0
\\DB04\Process(svchost)\IO Data Operations/sec | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0
\\DB04\Process(lsass)\IO Data Operations/sec | 0 | 67 | 1,978 | -6,905 | 234 | 8 | 2 | 2
\\DB04\Process(services)\IO Data Operations/sec | 0 | 1 | 13 | -41 | 3 | 1 | 0 | 0
\\DB04\Process(winlogon)\IO Data Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(csrss)\IO Data Operations/sec | 0 | 0 | 19 | -47 | 2 | 0 | - | -
\\DB04\Process(smss)\IO Data Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(System)\IO Data Operations/sec | 0 | 0 | 2 | -5 | 0 | 0 | 0 | 0
\\DB04\Process(Idle)\IO Data Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\Process(dfrgifc)\IO Data Operations/sec | 0 | 2 | 3 | -
* | OK | \\DB04\Process(powershell#4)\IO Data Operations/sec | - | - | - | -
* | OK | \\DB04\Process(cmd#4)\IO Data Operations/sec | - | - | - | -
* | OK | \\DB04\Process(powershell#3)\IO Data Operations/sec | - | - | - | -
* | OK | \\DB04\Process(cmd#3)\IO Data Operations/sec | - | - | - | -
* | OK | \\DB04\Process(powershell#2)\IO Data Operations/sec | 0 | 0 | 1 | 3
* | OK | \\DB04\Process(cmd#2)\IO Data Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(SQLCMD#1)\IO Data Operations/sec | - | - | - | -
* | OK | \\DB04\Process(SQLCMD)\IO Data Operations/sec | 0 | 13 | 147 | 39
* | OK | \\DB04\Process(msinfo32)\IO Data Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(cmd#1)\IO Data Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(SQLdiag)\IO Data Operations/sec | 0 | 1 | 2 | -3
* | OK | \\DB04\Process(powershell#1)\IO Data Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(cmd)\IO Data Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(explorer#1)\IO Data Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(svchost#8)\IO Data Operations/sec | 0 | 0 | 0 | 0
* | OK | \\DB04\Process(SQLAGENT)\IO Data Operations/sec | 0 | 1 | 2 | 0
* | OK | \\DB04\Process(fdhost)\IO Data Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(sqlservr)\IO Data Operations/sec | 0 | 21 | 350 | 410
* | OK | \\DB04\Process(Ssms)\IO Data Operations/sec | 0 | 1 | 2 | 2
* | OK | \\DB04\Process(wpabaln)\IO Data Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(powershell)\IO Data Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(wmiprvse#1)\IO Data Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(explorer)\IO Data Operations/sec | 0 | - | 0 | 0
12/16/2009 1:04:09 PM | This process is using more than 1000 data I/O's per second | \\DB04\Process(wmiprvse)\IO Data Operations/sec | 112 | 1,044 | 1,898 | 0
12/16/2009 1:04:09 PM | This process is using more than 1000 data I/O's per second | \\DB04\Process(lsass)\IO Data Operations/sec | 149 | 1,095 | 1,978 | 0

Back to the top

## Process IO Other Operations/sec

> Description: The rate at which the process is issuing I/O operations that are neither read nor write operations (for example, a control function). This counter counts all I/O activity generated by the process to include file, network and device I/Os.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\Process(_Total)\IO Other Operations/sec | 25 | 176 | 3,463 | -13,752 | 459 | 63 | 39 | 37
\\DB04\Process(dfrgifc)\IO Other Operations/sec | 0 | 11 | 22 | - | 0 | - | - | -
\\DB04\Process(powershell#4)\IO Other Operations/sec | - | - | - | - | - | - | - | -
\\DB04\Process(cmd#4)\IO Other Operations/sec | - | - | - | - | - | - | - | -
\\DB04\Process(powershell#3)\IO Other Operations/sec | - | - | - | - | - | - | - | -
\\DB04\Process(cmd#3)\IO Other Operations/sec | - | - | - | - | - | - | - | -
\\DB04\Process(powershell#2)\IO Other Operations/sec | 0 | 2 | 5 | 8 | 0 | 2 | 2 | 1
\\DB04\Process(cmd#2)\IO Other Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(SQLCMD#1)\IO Other Operations/sec | - | - | - | - | - | - | - | -
\\DB04\Process(SQLCMD)\IO Other Operations/sec | 0 | 0 | 0 | 0 | 0 | - | - | -
\\DB04\Process(msinfo32)\IO Other Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(cmd#1)\IO Other Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(SQLdiag)\IO Other Operations/sec | 8 | 16 | 19 | -23 | 1 | 16 | 16 | 16
\\DB04\Process(powershell#1)\IO Other Operations/sec | 0 | 0 | 0 | 0 | 0 | - | - | -
\\DB04\Process(cmd)\IO Other Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(explorer#1)\IO Other Operations/sec | 0 | 0 | 19 | -41 | 1 | 0 | - | -
\\DB04\Process(svchost#8)\IO Other Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(SQLAGENT)\IO Other Operations/sec | 7 | 10 | 13 | -6 | 0 | 10 | 10 | 10
\\DB04\Process(fdhost)\IO Other Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(sqlservr)\IO Other Operations/sec | 0 | 6 | 117 | -34 | 16 | 3 | 1 | 0
\\DB04\Process(Ssms)\IO Other Operations/sec | 0 | 0 | 1 | -1 | 0 | - | - | -
\\DB04\Process(wpabaln)\IO Other Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(powershell)\IO Other Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(wmiprvse#1)\IO Other Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(explorer)\IO Other Operations/sec | 0 | 0 | 3 | -3 | 0 | 0 | 0 | 0
\\DB04\Process(wmiprvse)\IO Other Operations/sec | 0 | 58 | 1,163 | -5,500 | 180 | 16 | 0 | 0
\\DB04\Process(alg)\IO Other Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(fdlauncher)\IO Other Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(svchost#7)\IO Other Operations/sec | 0 | 0 | 1 | 0 | 0 | - | - | -
\\DB04\Process(sqlwriter)\IO Other Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(svchost#6)\IO Other Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(MsDtsSrvr)\IO Other Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(svchost#5)\IO Other Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(msdtc)\IO Other Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(vmicsvc#4)\IO Other Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(vmicsvc#3)\IO Other Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(vmicsvc#2)\IO Other Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(vmicsvc#1)\IO Other Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(vmicsvc)\IO Other Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(spoolsv)\IO Other Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(svchost#4)\IO Other Operations/sec | 0 | 5 | 297 | -784 | 22 | 1 | 1 | 0
\\DB04\Process(svchost#3)\IO Other Operations/sec | 0 | 0 | 3 | 1 | 0 | 0 | 0 | 0
\\DB04\Process(svchost#2)\IO Other Operations/sec | 0 | 0 | 10 | 0 | 1 | - | - | -
\\DB04\Process(svchost#1)\IO Other Operations/sec | 0 | 0 | 8 | -18 | 1 | 0 | - | -
\\DB04\Process(svchost)\IO Other Operations/sec | 0 | 0 | 6 | -13 | 0 | - | - | -
\\DB04\Process(lsass)\IO Other Operations/sec | 0 | 77 | 2,279 | -7,962 | 270 | 8 | 2 | 1
\\DB04\Process(services)\IO Other Operations/sec | 0 | 5 | 11 | -2 | 1 | 5 | 5 | 5
\\DB04\Process(winlogon)\IO Other Operations/sec | 0 | 0 | 1 | -2 | 0 | 0 | - | -
\\DB04\Process(csrss)\IO Other Operations/sec | 0 | 1 | 69 | -146 | 4 | - | - | -
\\DB04\Process(smss)\IO Other Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -
\\DB04\Process(System)\IO Other Operations/sec | 0 | 1 | 9 | -9 | 1 | 0 | 0 | 0
\\DB04\Process(Idle)\IO Other Operations/sec | 0 | - | 0 | 0 | 0 | - | - | -

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\Process(dfrgifc)\IO Other Operations/sec | 0 | 11 | 22 | -
* | OK | \\DB04\Process(powershell#4)\IO Other Operations/sec | - | - | - | -
* | OK | \\DB04\Process(cmd#4)\IO Other Operations/sec | - | - | - | -
* | OK | \\DB04\Process(powershell#3)\IO Other Operations/sec | - | - | - | -
* | OK | \\DB04\Process(cmd#3)\IO Other Operations/sec | - | - | - | -
* | OK | \\DB04\Process(powershell#2)\IO Other Operations/sec | 0 | 2 | 5 | 8
* | OK | \\DB04\Process(cmd#2)\IO Other Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(SQLCMD#1)\IO Other Operations/sec | - | - | - | -
* | OK | \\DB04\Process(SQLCMD)\IO Other Operations/sec | 0 | 0 | 0 | 0
* | OK | \\DB04\Process(msinfo32)\IO Other Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(cmd#1)\IO Other Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(SQLdiag)\IO Other Operations/sec | 8 | 16 | 19 | -23
* | OK | \\DB04\Process(powershell#1)\IO Other Operations/sec | 0 | 0 | 0 | 0
* | OK | \\DB04\Process(cmd)\IO Other Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(explorer#1)\IO Other Operations/sec | 0 | 0 | 19 | -41
* | OK | \\DB04\Process(svchost#8)\IO Other Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(SQLAGENT)\IO Other Operations/sec | 7 | 10 | 13 | -6
* | OK | \\DB04\Process(fdhost)\IO Other Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(sqlservr)\IO Other Operations/sec | 0 | 6 | 117 | -34
* | OK | \\DB04\Process(Ssms)\IO Other Operations/sec | 0 | 0 | 1 | -1
* | OK | \\DB04\Process(wpabaln)\IO Other Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(powershell)\IO Other Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(wmiprvse#1)\IO Other Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(explorer)\IO Other Operations/sec | 0 | 0 | 3 | -3
* | OK | \\DB04\Process(wmiprvse)\IO Other Operations/sec | 0 | 58 | 1,163 | -5,500
* | OK | \\DB04\Process(alg)\IO Other Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(fdlauncher)\IO Other Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(svchost#7)\IO Other Operations/sec | 0 | 0 | 1 | 0
* | OK | \\DB04\Process(sqlwriter)\IO Other Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(svchost#6)\IO Other Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(MsDtsSrvr)\IO Other Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(svchost#5)\IO Other Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(msdtc)\IO Other Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(vmicsvc#4)\IO Other Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(vmicsvc#3)\IO Other Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(vmicsvc#2)\IO Other Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(vmicsvc#1)\IO Other Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(vmicsvc)\IO Other Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(spoolsv)\IO Other Operations/sec | 0 | - | 0 | 0
* | OK | \\DB04\Process(svchost#4)\IO Other Operations/sec | 0 | 5 | 297 | -784
* | OK | \\DB04\Process(svchost#3)\IO Other Operations/sec | 0 | 0 | 3 | 1
* | OK | \\DB04\Process(svchost#2)\IO Other Operations/sec | 0 | 0 | 10 | 0
* | OK | \\DB04\Process(svchost#1)\IO Other Operations/sec | 0 | 0 | 8 | -18
* | OK | \\DB04\Process(svchost)\IO Other Operations/sec | 0 | 0 | 6 | -13
12/16/2009 1:04:09 PM | This process is using more than 1000 other I/O's per second | \\DB04\Process(lsass)\IO Other Operations/sec | 174 | 1,262 | 2,279 | 0

Back to the top

## LogicalDisk Disk Transfers/sec

> Description: Disk Transfers/sec is the rate of read and write operations on the disk.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\LogicalDisk(_Total)\Disk Transfers/sec | 1 | 29 | 362 | -393 | 30 | 24 | 21 | 21
\\DB04\LogicalDisk(P:)\Disk Transfers/sec | 0 | 1 | 6 | -12 | 0 | 1 | 1 | 1
\\DB04\LogicalDisk(T:)\Disk Transfers/sec | 0 | 1 | 10 | 25 | 1 | 1 | 1 | 1
\\DB04\LogicalDisk(S:)\Disk Transfers/sec | 0 | 14 | 326 | 357 | 18 | 11 | 10 | 10
\\DB04\LogicalDisk(C:)\Disk Transfers/sec | 1 | 13 | 303 | -763 | 22 | 8 | 8 | 8

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
12/16/2009 1:07:00 PM | Less than 80 I/O's per second on average when disk latency is longer than 25ms. This may indicate too many virtual LUNs using the same physical disks on a SAN. This was a spike - not an average. | \\DB04\LogicalDisk(_Total)\Disk Transfers/sec | 9 | 17 | 22 | -2,641
12/16/2009 1:07:00 PM | Less than 80 I/O's per second on average when disk latency is longer than 25ms. This may indicate too many virtual LUNs using the same physical disks on a SAN. This was a spike - not an average. | \\DB04\LogicalDisk(S:)\Disk Transfers/sec | 0 | 5 | 9 | -34

Back to the top

# Memory

## Free System Page Table Entries

> Description: Free System Page Table Entries is the number of page table entries not currently in used by the system. This analysis determines if the system is running out of free system page table entries (PTEs) by checking if there is less than 5,000 free PTE’s with a Warning if there is less than 10,000 free PTE’s. Lack of enough PTEs can result in system wide hangs. Also note that the /3GB switch will lower the amount of free PTEs significantly.
> The Performance Monitor “Memory\Free System Page Table Entries” counter is inaccurate on installations of Windows Server 2003 without Service Pack 1. For more information about this counter, see Microsoft Knowledge Base article 894067 “The Performance tool does not accurately show the available Free System Page Table entries in Windows Server 2003” http://go.microsoft.com/fwlink/?linkid=3052&kbid=894067
> Fix for Win2003 SP1 systems with /3GB and low on PTE’s: If the system is low on PTE’s, running Windows 2003, and using /3GB switch, then consider using the /USERVA switch to give back some of the memory to the kernel. Note, this only works for Free System PTE issues.
> For more information on the USERVA switch, go to: How to use the /userva switch with the /3GB switch to tune the User-mode space to a value between 2 GB and 3 GB http://support.microsoft.com/kb/316739
> Reference:
> Ruling Out Memory-Bound Problems
> http://technet.microsoft.com/en-us/library/7a44b064-8872-4edf-aac7-36b2a17f662a.aspx
> Microsoft Knowledge Base article 894067 “The Performance tool does not accurately show the available Free System Page Table entries in Windows Server 2003” http://go.microsoft.com/fwlink/?linkid=3052&kbid=894067
> “How to use the /userva switch with the /3GB switch to tune the User-mode space to a value between 2 GB and 3 GB” http://support.microsoft.com/kb/316739">http://support.microsoft.com/kb/316739
> How to determine the appropriate page file size for 64-bit versions of Windows Server 2003 or Windows XP
> http://support.microsoft.com/kb/889654

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\Memory\Free System Page Table Entries | 2,081,709 | 2,081,709 | 2,081,709 | 0 | 0 | 2,081,709 | 2,081,709 | 2,081,709

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\Memory\Free System Page Table Entries | 2,081,709 | 2,081,709 | 2,081,709 | 0

Back to the top

## Pool Non Paged Bytes

> Description: Pool Nonpaged Bytes is the size, in bytes, of the nonpaged pool, an area of system memory (physical memory used by the operating system) for objects that cannot be written to disk, but must remain in physical memory as long as they are allocated.
> This analysis checks to see if the system is becoming close to the maximum Pool Nonpaged memory size. It does this by estimating the pool sizes taking into consideration /3GB, physical memory size, and 32-bit/64-bit, then determining if the value is higher than 60% of the estimated pool size. If the system becomes close to the maximum size, then the system could experience system wide hangs. Checks both 32-bit and 64-bit memory pools. Warning: The /3GB switch option in the boot.ini file significantly reduces the size of this memory pool.
> If the system is low on Paged Pool or non-Paged pool memory, then it is recommended to open a support case with Microsoft to address this. Alternatively, you can use a free and public tool called Poolmon.exe to see what DLL’s are using kernel memory (see the article below). Most kernel memory leaks can be tracked back to a usermode process. To identify which user mode process is responsible, reboot the system (so you start off with a clean system), start a performance monitor log intending to run for a week or more capturing the Memory and Process objects, then analyze the perfmon log looking for memory leaks and/or handle leaks in one or more of the processes. In any case, migrating to a 64-bit version of Windows should alleviate this issue.
> References:
> How to Use Memory Pool Monitor (Poolmon.exe) to Troubleshoot Kernel Mode Memory Leaks
> http://support.microsoft.com/kb/177415
> Ruling Out Memory-Bound Problems
> http://technet.microsoft.com/en-us/library/7a44b064-8872-4edf-aac7-36b2a17f662a.aspx
> How to determine the appropriate page file size for 64-bit versions of Windows Server 2003 or Windows XP
> http://support.microsoft.com/kb/889654

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\Memory\Pool Nonpaged Bytes | 22,511,616 | 22,556,221 | 22,757,376 | -258,695 | 28,994 | 22,554,401 | 22,551,774 | 22,551,040

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\Memory\Pool Nonpaged Bytes | 22,511,616 | 22,556,221 | 22,757,376 | -258,695

Back to the top

## Pool Paged Bytes

> Description: This analysis checks to see if the system is becoming close to the maximum Pool paged memory size. Pool Paged Bytes is the size, in bytes, of the paged pool, an area of system memory (physical memory used by the operating system) for objects that can be written to disk when they are not being used.
> This analysis checks to see if the system is becoming close to the maximum Pool Paged memory size. It does this by estimating the pool sizes taking into consideration /3GB, physical memory size, and 32-bit/64-bit, then determining if the value is higher than 60% of the estimated pool size. If the system becomes close to the maximum size, then the system could experience system wide hangs. Checks both 32-bit and 64-bit memory pools. Warning: The /3GB switch option in the boot.ini file significantly reduces the size of this memory pool.
> If the system is low on Paged Pool or non-Paged pool memory, then it is recommended to open a support case with Microsoft to address this. Alternatively, you can use a free and public tool called Poolmon.exe to see what DLL’s are using kernel memory (see the article below). Most kernel memory leaks can be tracked back to a usermode process. To identify which user mode process is responsible, reboot the system (so you start off with a clean system), start a performance monitor log intending to run for a week or more capturing the Memory and Process objects, then analyze the perfmon log looking for memory leaks and/or handle leaks in one or more of the processes. In any case, migrating to a 64-bit version of Windows should alleviate this issue.
> Reference:
> How to Use Memory Pool Monitor (Poolmon.exe) to Troubleshoot Kernel Mode Memory Leaks
> http://support.microsoft.com/kb/177415
> Ruling Out Memory-Bound Problems
> http://technet.microsoft.com/en-us/library/7a44b064-8872-4edf-aac7-36b2a17f662a.aspx
> How to determine the appropriate page file size for 64-bit versions of Windows Server 2003 or Windows XP
> http://support.microsoft.com/kb/889654

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\Memory\Pool Paged Bytes | 46,542,848 | 46,675,131 | 50,315,264 | -11,725,339 | 406,358 | 46,588,311 | 46,548,651 | 46,546,749

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\Memory\Pool Paged Bytes | 46,542,848 | 46,675,131 | 50,315,264 | -11,725,339

Back to the top

## Available Memory

> Description: Available MBytes is the amount of physical memory available to processes running on the computer, in Megabytes, rather than bytes as reported in Memory\Available Bytes. The Virtual Memory Manager continually adjusts the space used in physical memory and on disk to maintain a minimum number of available bytes for the operating system and processes. When available bytes are plentiful, the Virtual Memory Manager lets the working sets of processes grow, or keeps them stable by removing an old page for each new page added. When available bytes are few, the Virtual Memory Manager must trim the working sets of processes to maintain the minimum required. This analysis checks to see if the total available memory is low – Warning at 10% available and Critical at 5% available. A Warning is also alerted when a decreasing trend of 10MB’s per hour is detecting indicating a potential upcoming memory condition. Low physical memory can cause increased privileged mode CPU and system delays.
> Reference:
> Ruling Out Memory-Bound Problems
> http://technet.microsoft.com/en-us/library/7a44b064-8872-4edf-aac7-36b2a17f662a.aspx
> Detecting Memory Bottlenecks
> http://www.microsoft.com/resources/documentation/windowsnt/4/workstation/reskit/en-us/04memory.mspx?mfr=true

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\Memory\Available MBytes | 41 | 106 | 131 | 265 | 16 | 106 | 105 | 103

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
12/16/2009 1:04:09 PM | Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 41 | 73 | 86 | 0
12/16/2009 1:04:28 PM | Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 81 | 100 | 118 | 5,211
12/16/2009 1:04:47 PM | Low on available memory - less than 10% available | \\DB04\Memory\Available MBytes | 117 | 119 | 121 | 4,389
12/16/2009 1:05:06 PM | Low on available memory - less than 10% available | \\DB04\Memory\Available MBytes | 131 | 131 | 131 | 3,663
12/16/2009 1:05:25 PM | Low on available memory - less than 10% available | \\DB04\Memory\Available MBytes | 131 | 131 | 131 | 2,747
12/16/2009 1:05:44 PM | Low on available memory - less than 10% available | \\DB04\Memory\Available MBytes | 131 | 131 | 131 | 2,198
12/16/2009 1:06:03 PM | Low on available memory - less than 10% available | \\DB04\Memory\Available MBytes | 131 | 131 | 131 | 1,832
12/16/2009 1:06:22 PM | Low on available memory - less than 10% available | \\DB04\Memory\Available MBytes | 131 | 131 | 131 | 1,570
12/16/2009 1:06:41 PM | Low on available memory - less than 10% available | \\DB04\Memory\Available MBytes | 128 | 129 | 131 | 1,320
12/16/2009 1:07:00 PM | Low on available memory - less than 10% available | \\DB04\Memory\Available MBytes | 117 | 123 | 128 | 1,047
12/16/2009 1:07:19 PM | Low on available memory - less than 10% available | \\DB04\Memory\Available MBytes | 117 | 117 | 117 | 834
12/16/2009 1:07:38 PM | Low on available memory - less than 10% available | \\DB04\Memory\Available MBytes | 117 | 117 | 117 | 758
12/16/2009 1:07:57 PM | Low on available memory - less than 10% available | \\DB04\Memory\Available MBytes | 116 | 116 | 117 | 683
12/16/2009 1:08:16 PM | Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 97 | 111 | 116 | 557
12/16/2009 1:08:35 PM | Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 93 | 94 | 94 | 281
12/16/2009 1:08:54 PM | Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 94 | 94 | 94 | 265
12/16/2009 1:09:13 PM | Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 94 | 94 | 94 | 249
12/16/2009 1:09:32 PM | Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 93 | 94 | 94 | 231
12/16/2009 1:09:51 PM | Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 93 | 93 | 93 | 211
12/16/2009 1:10:10 PM | Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 93 | 93 | 93 | 199
12/16/2009 1:10:29 PM | Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 93 | 93 | 93 | 189
12/16/2009 1:10:48 PM | Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 92 | 93 | 95 | 180
12/16/2009 1:11:07 PM | Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 94 | 94 | 95 | 185
12/16/2009 1:11:26 PM | Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 94 | 94 | 94 | 173
12/16/2009 1:11:45 PM | Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 94 | 94 | 94 | 166
12/16/2009 1:12:04 PM | Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 94 | 94 | 94 | 159
12/16/2009 1:12:23 PM | Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 94 | 94 | 94 | 153
12/16/2009 1:12:42 PM | Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 94 | 95 | 96 | 154
12/16/2009 1:13:01 PM | Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 97 | 97 | 97 | 162
12/16/2009 1:13:20 PM | Very low on available memory - less than 5% available | \\DB04\Memory\Available MBytes | 97 | 99 | 103 | 170
12/16/2009 1:13:39 PM | Low on available memory - less than 10% available | \\DB04\Memory\Available MBytes | 115 | 115 | 115 | 265

Back to the top

## Memory Pages/sec

> Description: This analysis checks to see if the Pages/sec is high. If it is high, then the system is likely running out of memory by trying to page the memory to the disk. Pages/sec is the rate at which pages are read from or written to disk to resolve hard page faults. This counter is a primary indicator of the kinds of faults that cause system-wide delays. It is the sum of Memory\Pages Input/sec and Memory\Pages Output/sec. It is counted in numbers of pages, so it can be compared to other counts of pages, such as Memory\Page Faults/sec, without conversion. It includes pages retrieved to satisfy faults in the file system cache (usually requested by applications) non-cached mapped memory files.
> This counter should always be below 1000, therefore this analysis checks for values above 1000. Use this analysis in correlation with Available Memory Analysis and Memory Leak Analysis. All are throwing alerts at the same time, then this may indicate the system is running out of memory and the suspected processes involved and follow analysis steps mentioned in the Memory Leak analysis.
> Reference:
> Ruling Out Memory-Bound Problems
> http://technet.microsoft.com/en-us/library/7a44b064-8872-4edf-aac7-36b2a17f662a.aspx

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\Memory\Pages/sec | 0 | 13 | 259 | -1,204 | 42 | 2 | 0 | 0

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\Memory\Pages/sec | 0 | 13 | 259 | -1,204

Back to the top

## Memory Leak Detection

> Description: This analysis determines if any of the processes are consuming a large size of the system's memory and if the process is increasing in memory consumption over time. A process consuming large portions of memory is okay as long as the process returns the memory back to the system. Look for increasing trends in the chart. An increasing trend over a long period of time could indicate a memory leak. Private Bytes is the current size, in bytes, of memory that this process has allocated that cannot be shared with other processes. This analysis checks for a 10MB’s per hour and 5MB’s per hour increasing trends. Use this analysis in correlation with the Available Memory analysis.
> Also, keep in mind that newly started processes will initially appear as a memory leak when it is simply normal start up behavior. A memory leak is when a process continues to consume memory and not releasing memory over a long period of time.
> Use this analysis in correlation with the Available Memory analysis. If you suspect a memory leak condition, then install and use the Debug Diag tool. For more information on the Debug Diag Tool, see the references section.
> References:
> Debug Diagnostic Tool v1.1 http://www.microsoft.com/downloads/details.aspx?FamilyID=28bd5941-c458-46f1-b24d-f60151d875a3&displaylang=en

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\Process(_Total)\Private Bytes | 2,049,900,544 | 2,119,122,129 | 2,203,430,912 | 3,621,726 | 35,631,590 | 2,124,755,272 | 2,131,425,314 | 2,136,269,385
\\DB04\Process(dfrgifc)\Private Bytes | 1,515,520 | 1,650,688 | 1,732,608 | - | 0 | - | - | -
\\DB04\Process(powershell#4)\Private Bytes | 52,613,120 | 52,613,120 | 52,613,120 | - | 0 | - | - | -
\\DB04\Process(cmd#4)\Private Bytes | 1,978,368 | 1,978,368 | 1,978,368 | - | 0 | - | - | -
\\DB04\Process(powershell#3)\Private Bytes | 50,417,664 | 50,417,664 | 50,417,664 | - | 0 | - | - | -
\\DB04\Process(cmd#3)\Private Bytes | 1,978,368 | 1,978,368 | 1,978,368 | - | 0 | - | - | -
\\DB04\Process(powershell#2)\Private Bytes | 51,720,192 | 53,468,678 | 55,861,248 | 14,687,394 | 1,181,579 | 53,486,894 | 53,444,233 | 53,411,255
\\DB04\Process(cmd#2)\Private Bytes | 1,978,368 | 1,978,368 | 1,978,368 | 0 | 0 | 1,978,368 | 1,978,368 | 1,978,368
\\DB04\Process(SQLCMD#1)\Private Bytes | 4,366,336 | 4,366,336 | 4,366,336 | - | 0 | - | - | -
\\DB04\Process(SQLCMD)\Private Bytes | 4,878,336 | 4,908,296 | 4,935,680 | -232,825 | 13,313 | 4,907,914 | 4,905,728 | 4,903,424
\\DB04\Process(msinfo32)\Private Bytes | 4,231,168 | 7,749,746 | 9,240,576 | 262,154,779 | 1,176,131 | 7,749,746 | 8,557,227 | 8,557,227
\\DB04\Process(cmd#1)\Private Bytes | 1,978,368 | 2,157,535 | 3,829,760 | -11,693,002 | 547,364 | 2,049,575 | 1,978,368 | 1,978,368
\\DB04\Process(SQLdiag)\Private Bytes | 16,678,912 | 16,891,475 | 16,945,152 | 866,627 | 48,071 | 16,895,134 | 16,894,054 | 16,891,465
\\DB04\Process(powershell#1)\Private Bytes | 52,850,688 | 52,867,534 | 52,899,840 | -310,434 | 19,614 | 52,866,993 | 52,864,512 | 52,862,098
\\DB04\Process(cmd)\Private Bytes | 1,974,272 | 1,974,272 | 1,974,272 | 0 | 0 | 1,974,272 | 1,974,272 | 1,974,272
\\DB04\Process(explorer#1)\Private Bytes | 7,897,088 | 7,947,033 | 8,044,544 | -931,301 | 47,559 | 7,945,295 | 7,944,090 | 7,948,434
\\DB04\Process(svchost#8)\Private Bytes | 3,960,832 | 3,960,832 | 3,960,832 | 0 | 0 | 3,960,832 | 3,960,832 | 3,960,832
\\DB04\Process(SQLAGENT)\Private Bytes | 24,678,400 | 24,813,172 | 24,817,664 | 879,562 | 24,606 | 24,817,664 | 24,817,664 | 24,817,664
\\DB04\Process(fdhost)\Private Bytes | 5,095,424 | 5,143,783 | 5,144,576 | 0 | 3,019 | 5,144,576 | 5,144,576 | 5,144,576
\\DB04\Process(sqlservr)\Private Bytes | 1,441,280,000 | 1,508,957,283 | 1,538,826,240 | 270,930,998 | 37,566,274 | 1,514,361,777 | 1,520,990,106 | 1,527,363,218
\\DB04\Process(Ssms)\Private Bytes | 196,517,888 | 196,620,585 | 196,694,016 | 898,964 | 69,384 | 196,626,786 | 196,633,037 | 196,637,550
\\DB04\Process(wpabaln)\Private Bytes | 1,257,472 | 1,257,472 | 1,257,472 | 0 | 0 | 1,257,472 | 1,257,472 | 1,257,472
\\DB04\Process(powershell)\Private Bytes | 34,664,448 | 34,664,448 | 34,664,448 | 0 | 0 | 34,664,448 | 34,664,448 | 34,664,448
\\DB04\Process(wmiprvse#1)\Private Bytes | 2,936,832 | 2,936,832 | 2,936,832 | 0 | 0 | 2,936,832 | 2,936,832 | 2,936,832
\\DB04\Process(explorer)\Private Bytes | 10,997,760 | 11,039,975 | 11,071,488 | -465,651 | 36,020 | 11,042,422 | 11,044,762 | 11,049,106
\\DB04\Process(wmiprvse)\Private Bytes | 21,368,832 | 23,953,815 | 29,921,280 | -19,938,897 | 744,948 | 23,914,772 | 23,916,612 | 23,995,051
\\DB04\Process(alg)\Private Bytes | 1,425,408 | 1,425,408 | 1,425,408 | 0 | 0 | 1,425,408 | 1,425,408 | 1,425,408
\\DB04\Process(fdlauncher)\Private Bytes | 1,191,936 | 1,191,936 | 1,191,936 | 0 | 0 | 1,191,936 | 1,191,936 | 1,191,936
\\DB04\Process(svchost#7)\Private Bytes | 2,670,592 | 2,748,945 | 2,768,896 | -310,434 | 37,175 | 2,756,450 | 2,765,824 | 2,768,896
\\DB04\Process(sqlwriter)\Private Bytes | 1,949,696 | 1,949,696 | 1,949,696 | 0 | 0 | 1,949,696 | 1,949,696 | 1,949,696
\\DB04\Process(svchost#6)\Private Bytes | 917,504 | 917,504 | 917,504 | 0 | 0 | 917,504 | 917,504 | 917,504
\\DB04\Process(MsDtsSrvr)\Private Bytes | 50,216,960 | 50,216,960 | 50,216,960 | 0 | 0 | 50,216,960 | 50,216,960 | 50,216,960
\\DB04\Process(svchost#5)\Private Bytes | 1,134,592 | 1,134,592 | 1,134,592 | 0 | 0 | 1,134,592 | 1,134,592 | 1,134,592
\\DB04\Process(msdtc)\Private Bytes | 2,695,168 | 2,695,168 | 2,695,168 | 0 | 0 | 2,695,168 | 2,695,168 | 2,695,168
\\DB04\Process(vmicsvc#4)\Private Bytes | 3,207,168 | 3,207,168 | 3,207,168 | 0 | 0 | 3,207,168 | 3,207,168 | 3,207,168
\\DB04\Process(vmicsvc#3)\Private Bytes | 3,137,536 | 3,137,536 | 3,137,536 | 0 | 0 | 3,137,536 | 3,137,536 | 3,137,536
\\DB04\Process(vmicsvc#2)\Private Bytes | 3,121,152 | 3,121,152 | 3,121,152 | 0 | 0 | 3,121,152 | 3,121,152 | 3,121,152
\\DB04\Process(vmicsvc#1)\Private Bytes | 8,728,576 | 8,728,576 | 8,728,576 | 0 | 0 | 8,728,576 | 8,728,576 | 8,728,576
\\DB04\Process(vmicsvc)\Private Bytes | 4,042,752 | 4,042,752 | 4,042,752 | 0 | 0 | 4,042,752 | 4,042,752 | 4,042,752
\\DB04\Process(spoolsv)\Private Bytes | 5,046,272 | 5,154,794 | 5,177,344 | -827,823 | 48,208 | 5,165,581 | 5,177,344 | 5,177,344
\\DB04\Process(svchost#4)\Private Bytes | 27,455,488 | 28,915,943 | 33,697,792 | -14,060,059 | 1,131,964 | 28,945,211 | 28,950,784 | 28,968,667
\\DB04\Process(svchost#3)\Private Bytes | 2,371,584 | 2,374,359 | 2,420,736 | -310,434 | 10,680 | 2,371,584 | 2,371,584 | 2,371,584
\\DB04\Process(svchost#2)\Private Bytes | 6,037,504 | 6,037,504 | 6,037,504 | 0 | 0 | 6,037,504 | 6,037,504 | 6,037,504
\\DB04\Process(svchost#1)\Private Bytes | 2,228,224 | 2,266,013 | 2,277,376 | 77,608 | 19,567 | 2,269,499 | 2,274,509 | 2,277,376
\\DB04\Process(svchost)\Private Bytes | 1,540,096 | 1,580,792 | 1,589,248 | -310,434 | 18,078 | 1,584,837 | 1,589,248 | 1,589,248
\\DB04\Process(lsass)\Private Bytes | 12,435,456 | 12,508,479 | 12,591,104 | 459,183 | 42,102 | 12,509,092 | 12,509,116 | 12,514,962
\\DB04\Process(services)\Private Bytes | 6,664,192 | 6,720,842 | 6,762,496 | -594,998 | 41,662 | 6,724,175 | 6,727,424 | 6,732,581
\\DB04\Process(winlogon)\Private Bytes | 11,288,576 | 11,313,945 | 11,386,880 | -310,434 | 36,001 | 11,311,262 | 11,304,141 | 11,300,279
\\DB04\Process(csrss)\Private Bytes | 1,941,504 | 1,941,504 | 1,941,504 | 0 | 0 | 1,941,504 | 1,941,504 | 1,941,504
\\DB04\Process(smss)\Private Bytes | 253,952 | 253,952 | 253,952 | 0 | 0 | 253,952 | 253,952 | 253,952
\\DB04\Process(System)\Private Bytes | 94,208 | 94,208 | 94,208 | 0 | 0 | 94,208 | 94,208 | 94,208
\\DB04\Process(Idle)\Private Bytes | 0 | - | 0 | 0 | 0 | - | - | -

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\Process(dfrgifc)\Private Bytes | 1,515,520 | 1,650,688 | 1,732,608 | -
* | OK | \\DB04\Process(powershell#4)\Private Bytes | 52,613,120 | 52,613,120 | 52,613,120 | -
* | OK | \\DB04\Process(cmd#4)\Private Bytes | 1,978,368 | 1,978,368 | 1,978,368 | -
* | OK | \\DB04\Process(powershell#3)\Private Bytes | 50,417,664 | 50,417,664 | 50,417,664 | -
* | OK | \\DB04\Process(cmd#3)\Private Bytes | 1,978,368 | 1,978,368 | 1,978,368 | -
* | OK | \\DB04\Process(powershell#2)\Private Bytes | 51,720,192 | 53,468,678 | 55,861,248 | 14,687,394
* | OK | \\DB04\Process(cmd#2)\Private Bytes | 1,978,368 | 1,978,368 | 1,978,368 | 0
* | OK | \\DB04\Process(SQLCMD#1)\Private Bytes | 4,366,336 | 4,366,336 | 4,366,336 | -
* | OK | \\DB04\Process(SQLCMD)\Private Bytes | 4,878,336 | 4,908,296 | 4,935,680 | -232,825
* | OK | \\DB04\Process(msinfo32)\Private Bytes | 4,231,168 | 7,749,746 | 9,240,576 | 262,154,779
* | OK | \\DB04\Process(cmd#1)\Private Bytes | 1,978,368 | 2,157,535 | 3,829,760 | -11,693,002
* | OK | \\DB04\Process(SQLdiag)\Private Bytes | 16,678,912 | 16,891,475 | 16,945,152 | 866,627
* | OK | \\DB04\Process(powershell#1)\Private Bytes | 52,850,688 | 52,867,534 | 52,899,840 | -310,434
* | OK | \\DB04\Process(cmd)\Private Bytes | 1,974,272 | 1,974,272 | 1,974,272 | 0
* | OK | \\DB04\Process(explorer#1)\Private Bytes | 7,897,088 | 7,947,033 | 8,044,544 | -931,301
* | OK | \\DB04\Process(svchost#8)\Private Bytes | 3,960,832 | 3,960,832 | 3,960,832 | 0
* | OK | \\DB04\Process(SQLAGENT)\Private Bytes | 24,678,400 | 24,813,172 | 24,817,664 | 879,562
* | OK | \\DB04\Process(fdhost)\Private Bytes | 5,095,424 | 5,143,783 | 5,144,576 | 0
12/16/2009 1:06:41 PM | Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,450,659,840 | 1,481,544,704 | 1,493,245,952 | 56,387,368.4210526
12/16/2009 1:07:00 PM | Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,492,819,968 | 1,499,601,920 | 1,508,446,208 | 430,274,021.052632
12/16/2009 1:07:19 PM | Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,508,077,568 | 1,508,388,864 | 1,508,675,584 | 553,736,084.210526
12/16/2009 1:07:38 PM | Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,508,528,128 | 1,512,427,520 | 1,514,430,464 | 572,961,806.698565
12/16/2009 1:07:57 PM | Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,514,323,968 | 1,514,323,968 | 1,514,323,968 | 555,158,905.263158
12/16/2009 1:08:16 PM | Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,514,323,968 | 1,519,169,536 | 1,533,706,240 | 583,078,037.246964
12/16/2009 1:08:35 PM | Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,629,632 | 1,538,629,632 | 1,538,629,632 | 804,799,326.31579
12/16/2009 1:08:54 PM | Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,629,632 | 1,538,629,632 | 1,538,629,632 | 751,146,037.894737
12/16/2009 1:09:13 PM | Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,629,632 | 1,538,629,632 | 1,538,629,632 | 704,199,410.526316
12/16/2009 1:09:32 PM | Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,629,632 | 1,538,629,632 | 1,538,629,632 | 662,775,915.789474
12/16/2009 1:09:51 PM | Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,629,632 | 1,538,629,632 | 1,538,629,632 | 625,955,031.578947
12/16/2009 1:10:10 PM | Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,629,632 | 1,538,629,632 | 1,538,629,632 | 593,010,029.916898
12/16/2009 1:10:29 PM | Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,695,168 | 1,538,695,168 | 1,538,695,168 | 563,980,395.789474
12/16/2009 1:10:48 PM | Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,695,168 | 1,538,695,168 | 1,538,695,168 | 537,124,186.466165
12/16/2009 1:11:07 PM | Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,695,168 | 1,538,695,168 | 1,538,695,168 | 512,709,450.717703
12/16/2009 1:11:26 PM | Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,695,168 | 1,538,695,168 | 1,538,695,168 | 490,417,735.469108
12/16/2009 1:11:45 PM | Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,695,168 | 1,538,695,168 | 1,538,695,168 | 469,983,663.157895
12/16/2009 1:12:04 PM | Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,695,168 | 1,538,695,168 | 1,538,695,168 | 451,184,316.631579
12/16/2009 1:12:23 PM | Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,695,168 | 1,538,695,168 | 1,538,695,168 | 433,831,073.684211
12/16/2009 1:12:42 PM | Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,695,168 | 1,538,695,168 | 1,538,695,168 | 417,763,256.140351
12/16/2009 1:13:01 PM | Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,538,695,168 | 1,538,727,936 | 1,538,826,240 | 403,064,878.195489
12/16/2009 1:13:20 PM | Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,532,592,128 | 1,536,638,976 | 1,538,695,168 | 375,517,711.796733
12/16/2009 1:13:39 PM | Memory: an increasing trend of 10MB's per hour detected | \\DB04\Process(sqlservr)\Private Bytes | 1,520,164,864 | 1,522,061,312 | 1,523,957,760 | 270,930,997.894737

Back to the top

## Handle Leak Detection

> Description: This analysis checks all of the processes to determine how many handles each has open and determines if a handle leaks is suspected. A process with a large number of handles and/or an aggresive upward trend could indicate a handle leak which typically results in a memory leak. The total number of handles currently open by this process. This number is equal to the sum of the handles currently open by each thread in this process.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\Process(_Total)\Handle Count | 12,913 | 13,039 | 13,638 | -2,482 | 83 | 13,036 | 13,040 | 13,051
\\DB04\Process(dfrgifc)\Handle Count | 71 | 94 | 106 | - | 0 | - | - | -
\\DB04\Process(powershell#4)\Handle Count | 216 | 216 | 216 | - | 0 | - | - | -
\\DB04\Process(cmd#4)\Handle Count | 35 | 35 | 35 | - | 0 | - | - | -
\\DB04\Process(powershell#3)\Handle Count | 215 | 215 | 215 | - | 0 | - | - | -
\\DB04\Process(cmd#3)\Handle Count | 35 | 35 | 35 | - | 0 | - | - | -
\\DB04\Process(powershell#2)\Handle Count | 217 | 225 | 229 | 57 | 3 | 226 | 226 | 225
\\DB04\Process(cmd#2)\Handle Count | 35 | 35 | 35 | 0 | 0 | 35 | 35 | 35
\\DB04\Process(SQLCMD#1)\Handle Count | 136 | 136 | 136 | - | 0 | - | - | -
\\DB04\Process(SQLCMD)\Handle Count | 133 | 133 | 137 | -25 | 1 | 133 | 133 | 133
\\DB04\Process(msinfo32)\Handle Count | 98 | 99 | 100 | 63 | 0 | 99 | 100 | 100
\\DB04\Process(cmd#1)\Handle Count | 35 | 42 | 109 | -467 | 22 | 38 | 35 | 35
\\DB04\Process(SQLdiag)\Handle Count | 278 | 278 | 280 | -3 | 0 | 278 | 278 | 278
\\DB04\Process(powershell#1)\Handle Count | 235 | 237 | 242 | -32 | 2 | 237 | 237 | 237
\\DB04\Process(cmd)\Handle Count | 30 | 30 | 30 | 0 | 0 | 30 | 30 | 30
\\DB04\Process(explorer#1)\Handle Count | 270 | 271 | 273 | -19 | 1 | 271 | 271 | 271
\\DB04\Process(svchost#8)\Handle Count | 227 | 227 | 227 | 0 | 0 | 227 | 227 | 227
\\DB04\Process(SQLAGENT)\Handle Count | 370 | 370 | 370 | 0 | 0 | 370 | 370 | 370
\\DB04\Process(fdhost)\Handle Count | 136 | 136 | 136 | 0 | 0 | 136 | 136 | 136
\\DB04\Process(sqlservr)\Handle Count | 643 | 745 | 789 | 889 | 57 | 754 | 766 | 779
\\DB04\Process(Ssms)\Handle Count | 802 | 809 | 816 | 2 | 3 | 809 | 809 | 809
\\DB04\Process(wpabaln)\Handle Count | 41 | 41 | 41 | 0 | 0 | 41 | 41 | 41
\\DB04\Process(powershell)\Handle Count | 421 | 421 | 421 | 0 | 0 | 421 | 421 | 421
\\DB04\Process(wmiprvse#1)\Handle Count | 159 | 159 | 159 | 0 | 0 | 159 | 159 | 159
\\DB04\Process(explorer)\Handle Count | 426 | 429 | 430 | 0 | 1 | 429 | 429 | 429
\\DB04\Process(wmiprvse)\Handle Count | 1,409 | 1,691 | 1,709 | 341 | 17 | 1,693 | 1,693 | 1,695
\\DB04\Process(alg)\Handle Count | 88 | 88 | 88 | 0 | 0 | 88 | 88 | 88
\\DB04\Process(fdlauncher)\Handle Count | 37 | 37 | 37 | 0 | 0 | 37 | 37 | 37
\\DB04\Process(svchost#7)\Handle Count | 145 | 149 | 154 | -44 | 2 | 149 | 149 | 149
\\DB04\Process(sqlwriter)\Handle Count | 83 | 83 | 83 | 0 | 0 | 83 | 83 | 83
\\DB04\Process(svchost#6)\Handle Count | 42 | 42 | 42 | 0 | 0 | 42 | 42 | 42
\\DB04\Process(MsDtsSrvr)\Handle Count | 163 | 163 | 163 | 0 | 0 | 163 | 163 | 163
\\DB04\Process(svchost#5)\Handle Count | 69 | 69 | 69 | 0 | 0 | 69 | 69 | 69
\\DB04\Process(msdtc)\Handle Count | 153 | 153 | 153 | 0 | 0 | 153 | 153 | 153
\\DB04\Process(vmicsvc#4)\Handle Count | 88 | 88 | 88 | 0 | 0 | 88 | 88 | 88
\\DB04\Process(vmicsvc#3)\Handle Count | 87 | 87 | 87 | 0 | 0 | 87 | 87 | 87
\\DB04\Process(vmicsvc#2)\Handle Count | 78 | 78 | 78 | 0 | 0 | 78 | 78 | 78
\\DB04\Process(vmicsvc#1)\Handle Count | 154 | 154 | 154 | 0 | 0 | 154 | 154 | 154
\\DB04\Process(vmicsvc)\Handle Count | 102 | 102 | 102 | 0 | 0 | 102 | 102 | 102
\\DB04\Process(spoolsv)\Handle Count | 123 | 126 | 127 | -24 | 1 | 127 | 127 | 127
\\DB04\Process(svchost#4)\Handle Count | 1,284 | 1,349 | 1,374 | -325 | 21 | 1,355 | 1,356 | 1,358
\\DB04\Process(svchost#3)\Handle Count | 188 | 189 | 192 | -25 | 1 | 188 | 188 | 188
\\DB04\Process(svchost#2)\Handle Count | 150 | 152 | 155 | -9 | 1 | 152 | 152 | 152
\\DB04\Process(svchost#1)\Handle Count | 256 | 264 | 277 | -98 | 5 | 264 | 264 | 264
\\DB04\Process(svchost)\Handle Count | 89 | 91 | 91 | -13 | 1 | 91 | 91 | 91
\\DB04\Process(lsass)\Handle Count | 702 | 711 | 741 | -212 | 9 | 710 | 709 | 708
\\DB04\Process(services)\Handle Count | 367 | 370 | 375 | -35 | 2 | 370 | 370 | 370
\\DB04\Process(winlogon)\Handle Count | 685 | 686 | 692 | -44 | 2 | 686 | 686 | 685
\\DB04\Process(csrss)\Handle Count | 633 | 648 | 688 | -153 | 8 | 648 | 648 | 648
\\DB04\Process(smss)\Handle Count | 19 | 19 | 19 | 0 | 0 | 19 | 19 | 19
\\DB04\Process(System)\Handle Count | 868 | 877 | 884 | 55 | 5 | 878 | 879 | 879
\\DB04\Process(Idle)\Handle Count | 0 | - | 0 | 0 | 0 | - | - | -

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\Process(dfrgifc)\Handle Count | 71 | 94 | 106 | -
* | OK | \\DB04\Process(powershell#4)\Handle Count | 216 | 216 | 216 | -
* | OK | \\DB04\Process(cmd#4)\Handle Count | 35 | 35 | 35 | -
* | OK | \\DB04\Process(powershell#3)\Handle Count | 215 | 215 | 215 | -
* | OK | \\DB04\Process(cmd#3)\Handle Count | 35 | 35 | 35 | -
* | OK | \\DB04\Process(powershell#2)\Handle Count | 217 | 225 | 229 | 57
* | OK | \\DB04\Process(cmd#2)\Handle Count | 35 | 35 | 35 | 0
* | OK | \\DB04\Process(SQLCMD#1)\Handle Count | 136 | 136 | 136 | -
* | OK | \\DB04\Process(SQLCMD)\Handle Count | 133 | 133 | 137 | -25
* | OK | \\DB04\Process(msinfo32)\Handle Count | 98 | 99 | 100 | 63
* | OK | \\DB04\Process(cmd#1)\Handle Count | 35 | 42 | 109 | -467
* | OK | \\DB04\Process(SQLdiag)\Handle Count | 278 | 278 | 280 | -3
* | OK | \\DB04\Process(powershell#1)\Handle Count | 235 | 237 | 242 | -32
* | OK | \\DB04\Process(cmd)\Handle Count | 30 | 30 | 30 | 0
* | OK | \\DB04\Process(explorer#1)\Handle Count | 270 | 271 | 273 | -19
* | OK | \\DB04\Process(svchost#8)\Handle Count | 227 | 227 | 227 | 0
* | OK | \\DB04\Process(SQLAGENT)\Handle Count | 370 | 370 | 370 | 0
* | OK | \\DB04\Process(fdhost)\Handle Count | 136 | 136 | 136 | 0
* | OK | \\DB04\Process(sqlservr)\Handle Count | 643 | 745 | 789 | 889
* | OK | \\DB04\Process(Ssms)\Handle Count | 802 | 809 | 816 | 2
* | OK | \\DB04\Process(wpabaln)\Handle Count | 41 | 41 | 41 | 0
* | OK | \\DB04\Process(powershell)\Handle Count | 421 | 421 | 421 | 0
* | OK | \\DB04\Process(wmiprvse#1)\Handle Count | 159 | 159 | 159 | 0
* | OK | \\DB04\Process(explorer)\Handle Count | 426 | 429 | 430 | 0
* | OK | \\DB04\Process(wmiprvse)\Handle Count | 1,409 | 1,691 | 1,709 | 341
* | OK | \\DB04\Process(alg)\Handle Count | 88 | 88 | 88 | 0
* | OK | \\DB04\Process(fdlauncher)\Handle Count | 37 | 37 | 37 | 0
* | OK | \\DB04\Process(svchost#7)\Handle Count | 145 | 149 | 154 | -44
* | OK | \\DB04\Process(sqlwriter)\Handle Count | 83 | 83 | 83 | 0
* | OK | \\DB04\Process(svchost#6)\Handle Count | 42 | 42 | 42 | 0
* | OK | \\DB04\Process(MsDtsSrvr)\Handle Count | 163 | 163 | 163 | 0
* | OK | \\DB04\Process(svchost#5)\Handle Count | 69 | 69 | 69 | 0
* | OK | \\DB04\Process(msdtc)\Handle Count | 153 | 153 | 153 | 0
* | OK | \\DB04\Process(vmicsvc#4)\Handle Count | 88 | 88 | 88 | 0
* | OK | \\DB04\Process(vmicsvc#3)\Handle Count | 87 | 87 | 87 | 0
* | OK | \\DB04\Process(vmicsvc#2)\Handle Count | 78 | 78 | 78 | 0
* | OK | \\DB04\Process(vmicsvc#1)\Handle Count | 154 | 154 | 154 | 0
* | OK | \\DB04\Process(vmicsvc)\Handle Count | 102 | 102 | 102 | 0
* | OK | \\DB04\Process(spoolsv)\Handle Count | 123 | 126 | 127 | -24
* | OK | \\DB04\Process(svchost#4)\Handle Count | 1,284 | 1,349 | 1,374 | -325
* | OK | \\DB04\Process(svchost#3)\Handle Count | 188 | 189 | 192 | -25
* | OK | \\DB04\Process(svchost#2)\Handle Count | 150 | 152 | 155 | -9
* | OK | \\DB04\Process(svchost#1)\Handle Count | 256 | 264 | 277 | -98
* | OK | \\DB04\Process(svchost)\Handle Count | 89 | 91 | 91 | -13
* | OK | \\DB04\Process(lsass)\Handle Count | 702 | 711 | 741 | -212
* | OK | \\DB04\Process(services)\Handle Count | 367 | 370 | 375 | -35
* | OK | \\DB04\Process(winlogon)\Handle Count | 685 | 686 | 692 | -44
* | OK | \\DB04\Process(csrss)\Handle Count | 633 | 648 | 688 | -153
* | OK | \\DB04\Process(smss)\Handle Count | 19 | 19 | 19 | 0

Back to the top

## Process Thread Count

> Description: The number of threads currently active in this process. An instruction is the basic unit of execution in a processor, and a thread is the object that executes instructions. Every running process has at least one thread.
> This analysis checks all of the processes to determine if a process has more than 500 threads and if it is on an increasing trend of 50 threads per hour. A process with a large number of threads and/or an aggressive upward trend could indicate a thread leak which typically results in either a memory leak or high context switching. High context switching will result in high privileged mode CPU.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\Process(_Total)\Thread Count | 521 | 535 | 561 | -104 | 7 | 536 | 535 | 535
\\DB04\Process(dfrgifc)\Thread Count | 6 | 6 | 7 | - | 0 | - | - | -
\\DB04\Process(powershell#4)\Thread Count | 8 | 8 | 8 | - | 0 | - | - | -
\\DB04\Process(cmd#4)\Thread Count | 1 | 1 | 1 | - | 0 | - | - | -
\\DB04\Process(powershell#3)\Thread Count | 8 | 8 | 8 | - | 0 | - | - | -
\\DB04\Process(cmd#3)\Thread Count | 1 | 1 | 1 | - | 0 | - | - | -
\\DB04\Process(powershell#2)\Thread Count | 7 | 8 | 8 | -6 | 0 | 8 | 8 | 8
\\DB04\Process(cmd#2)\Thread Count | 1 | 1 | 1 | 0 | 0 | 1 | 1 | 1
\\DB04\Process(SQLCMD#1)\Thread Count | 5 | 5 | 5 | - | 0 | - | - | -
\\DB04\Process(SQLCMD)\Thread Count | 3 | 4 | 5 | -13 | 1 | 4 | 4 | 4
\\DB04\Process(msinfo32)\Thread Count | 6 | 6 | 6 | 0 | 0 | 6 | 6 | 6
\\DB04\Process(cmd#1)\Thread Count | 1 | 1 | 2 | -6 | 0 | 1 | 1 | 1
\\DB04\Process(SQLdiag)\Thread Count | 4 | 5 | 5 | -6 | 0 | 5 | 5 | 5
\\DB04\Process(powershell#1)\Thread Count | 6 | 7 | 8 | -13 | 1 | 7 | 7 | 6
\\DB04\Process(cmd)\Thread Count | 1 | 1 | 1 | 0 | 0 | 1 | 1 | 1
\\DB04\Process(explorer#1)\Thread Count | 4 | 5 | 6 | -13 | 1 | 5 | 5 | 5
\\DB04\Process(svchost#8)\Thread Count | 16 | 16 | 16 | 0 | 0 | 16 | 16 | 16
\\DB04\Process(SQLAGENT)\Thread Count | 14 | 14 | 14 | 0 | 0 | 14 | 14 | 14
\\DB04\Process(fdhost)\Thread Count | 5 | 6 | 6 | 0 | 0 | 6 | 6 | 6
\\DB04\Process(sqlservr)\Thread Count | 48 | 71 | 81 | 197 | 12 | 73 | 75 | 78
\\DB04\Process(Ssms)\Thread Count | 19 | 20 | 20 | 2 | 0 | 20 | 20 | 20
\\DB04\Process(wpabaln)\Thread Count | 1 | 1 | 1 | 0 | 0 | 1 | 1 | 1
\\DB04\Process(powershell)\Thread Count | 7 | 7 | 7 | 0 | 0 | 7 | 7 | 7
\\DB04\Process(wmiprvse#1)\Thread Count | 4 | 4 | 4 | 0 | 0 | 4 | 4 | 4
\\DB04\Process(explorer)\Thread Count | 9 | 10 | 10 | -6 | 0 | 10 | 10 | 10
\\DB04\Process(wmiprvse)\Thread Count | 16 | 18 | 20 | -17 | 1 | 18 | 18 | 18
\\DB04\Process(alg)\Thread Count | 5 | 5 | 5 | 0 | 0 | 5 | 5 | 5
\\DB04\Process(fdlauncher)\Thread Count | 1 | 1 | 1 | 0 | 0 | 1 | 1 | 1
\\DB04\Process(svchost#7)\Thread Count | 15 | 17 | 17 | -6 | 1 | 17 | 17 | 17
\\DB04\Process(sqlwriter)\Thread Count | 3 | 3 | 3 | 0 | 0 | 3 | 3 | 3
\\DB04\Process(svchost#6)\Thread Count | 2 | 2 | 2 | 0 | 0 | 2 | 2 | 2
\\DB04\Process(MsDtsSrvr)\Thread Count | 6 | 6 | 6 | 0 | 0 | 6 | 6 | 6
\\DB04\Process(svchost#5)\Thread Count | 2 | 2 | 2 | 0 | 0 | 2 | 2 | 2
\\DB04\Process(msdtc)\Thread Count | 13 | 13 | 13 | 0 | 0 | 13 | 13 | 13
\\DB04\Process(vmicsvc#4)\Thread Count | 3 | 3 | 3 | 0 | 0 | 3 | 3 | 3
\\DB04\Process(vmicsvc#3)\Thread Count | 3 | 3 | 3 | 0 | 0 | 3 | 3 | 3
\\DB04\Process(vmicsvc#2)\Thread Count | 3 | 3 | 3 | 0 | 0 | 3 | 3 | 3
\\DB04\Process(vmicsvc#1)\Thread Count | 5 | 5 | 5 | 0 | 0 | 5 | 5 | 5
\\DB04\Process(vmicsvc)\Thread Count | 3 | 3 | 3 | 0 | 0 | 3 | 3 | 3
\\DB04\Process(spoolsv)\Thread Count | 11 | 13 | 13 | -13 | 1 | 13 | 13 | 13
\\DB04\Process(svchost#4)\Thread Count | 57 | 61 | 67 | -55 | 3 | 61 | 60 | 60
\\DB04\Process(svchost#3)\Thread Count | 15 | 15 | 16 | -6 | 0 | 15 | 15 | 15
\\DB04\Process(svchost#2)\Thread Count | 9 | 9 | 9 | 0 | 0 | 9 | 9 | 9
\\DB04\Process(svchost#1)\Thread Count | 10 | 11 | 11 | 2 | 0 | 11 | 11 | 11
\\DB04\Process(svchost)\Thread Count | 5 | 6 | 6 | -6 | 0 | 6 | 6 | 6
\\DB04\Process(lsass)\Thread Count | 31 | 32 | 33 | -6 | 1 | 32 | 32 | 32
\\DB04\Process(services)\Thread Count | 16 | 17 | 18 | -13 | 1 | 17 | 17 | 17
\\DB04\Process(winlogon)\Thread Count | 18 | 19 | 20 | -6 | 1 | 18 | 18 | 18
\\DB04\Process(csrss)\Thread Count | 15 | 15 | 15 | 0 | 0 | 15 | 15 | 15
\\DB04\Process(smss)\Thread Count | 3 | 3 | 3 | 0 | 0 | 3 | 3 | 3
\\DB04\Process(System)\Thread Count | 72 | 72 | 73 | -2 | 0 | 72 | 72 | 72
\\DB04\Process(Idle)\Thread Count | 2 | 2 | 2 | 0 | 0 | 2 | 2 | 2

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\Process(dfrgifc)\Thread Count | 6 | 6 | 7 | -
* | OK | \\DB04\Process(powershell#4)\Thread Count | 8 | 8 | 8 | -
* | OK | \\DB04\Process(cmd#4)\Thread Count | 1 | 1 | 1 | -
* | OK | \\DB04\Process(powershell#3)\Thread Count | 8 | 8 | 8 | -
* | OK | \\DB04\Process(cmd#3)\Thread Count | 1 | 1 | 1 | -
* | OK | \\DB04\Process(powershell#2)\Thread Count | 7 | 8 | 8 | -6
* | OK | \\DB04\Process(cmd#2)\Thread Count | 1 | 1 | 1 | 0
* | OK | \\DB04\Process(SQLCMD#1)\Thread Count | 5 | 5 | 5 | -
* | OK | \\DB04\Process(SQLCMD)\Thread Count | 3 | 4 | 5 | -13
* | OK | \\DB04\Process(msinfo32)\Thread Count | 6 | 6 | 6 | 0
* | OK | \\DB04\Process(cmd#1)\Thread Count | 1 | 1 | 2 | -6
* | OK | \\DB04\Process(SQLdiag)\Thread Count | 4 | 5 | 5 | -6
* | OK | \\DB04\Process(powershell#1)\Thread Count | 6 | 7 | 8 | -13
* | OK | \\DB04\Process(cmd)\Thread Count | 1 | 1 | 1 | 0
* | OK | \\DB04\Process(explorer#1)\Thread Count | 4 | 5 | 6 | -13
* | OK | \\DB04\Process(svchost#8)\Thread Count | 16 | 16 | 16 | 0
* | OK | \\DB04\Process(SQLAGENT)\Thread Count | 14 | 14 | 14 | 0
* | OK | \\DB04\Process(fdhost)\Thread Count | 5 | 6 | 6 | 0
* | OK | \\DB04\Process(sqlservr)\Thread Count | 48 | 71 | 81 | 197
* | OK | \\DB04\Process(Ssms)\Thread Count | 19 | 20 | 20 | 2
* | OK | \\DB04\Process(wpabaln)\Thread Count | 1 | 1 | 1 | 0
* | OK | \\DB04\Process(powershell)\Thread Count | 7 | 7 | 7 | 0
* | OK | \\DB04\Process(wmiprvse#1)\Thread Count | 4 | 4 | 4 | 0
* | OK | \\DB04\Process(explorer)\Thread Count | 9 | 10 | 10 | -6
* | OK | \\DB04\Process(wmiprvse)\Thread Count | 16 | 18 | 20 | -17
* | OK | \\DB04\Process(alg)\Thread Count | 5 | 5 | 5 | 0
* | OK | \\DB04\Process(fdlauncher)\Thread Count | 1 | 1 | 1 | 0
* | OK | \\DB04\Process(svchost#7)\Thread Count | 15 | 17 | 17 | -6
* | OK | \\DB04\Process(sqlwriter)\Thread Count | 3 | 3 | 3 | 0
* | OK | \\DB04\Process(svchost#6)\Thread Count | 2 | 2 | 2 | 0
* | OK | \\DB04\Process(MsDtsSrvr)\Thread Count | 6 | 6 | 6 | 0
* | OK | \\DB04\Process(svchost#5)\Thread Count | 2 | 2 | 2 | 0
* | OK | \\DB04\Process(msdtc)\Thread Count | 13 | 13 | 13 | 0
* | OK | \\DB04\Process(vmicsvc#4)\Thread Count | 3 | 3 | 3 | 0
* | OK | \\DB04\Process(vmicsvc#3)\Thread Count | 3 | 3 | 3 | 0
* | OK | \\DB04\Process(vmicsvc#2)\Thread Count | 3 | 3 | 3 | 0
* | OK | \\DB04\Process(vmicsvc#1)\Thread Count | 5 | 5 | 5 | 0
* | OK | \\DB04\Process(vmicsvc)\Thread Count | 3 | 3 | 3 | 0
* | OK | \\DB04\Process(spoolsv)\Thread Count | 11 | 13 | 13 | -13
* | OK | \\DB04\Process(svchost#4)\Thread Count | 57 | 61 | 67 | -55
* | OK | \\DB04\Process(svchost#3)\Thread Count | 15 | 15 | 16 | -6
* | OK | \\DB04\Process(svchost#2)\Thread Count | 9 | 9 | 9 | 0
* | OK | \\DB04\Process(svchost#1)\Thread Count | 10 | 11 | 11 | 2
* | OK | \\DB04\Process(svchost)\Thread Count | 5 | 6 | 6 | -6
* | OK | \\DB04\Process(lsass)\Thread Count | 31 | 32 | 33 | -6
* | OK | \\DB04\Process(services)\Thread Count | 16 | 17 | 18 | -13
* | OK | \\DB04\Process(winlogon)\Thread Count | 18 | 19 | 20 | -6
* | OK | \\DB04\Process(csrss)\Thread Count | 15 | 15 | 15 | 0
* | OK | \\DB04\Process(smss)\Thread Count | 3 | 3 | 3 | 0

Back to the top

## High Virtual Memory Usage

> Description: This analysis determines if any of the processes are consuming a large of virtual memory. 32-bit processes by default are only allowed to access up to 2GB's of user mode memory. If the process becomes close to this maximum, then it could starve for memory. If a process is becoming close to it's maximum, then consider moving the process to a 64-bit system. The /3GB switch could be used to give the user mode process a total of 3GB's of addressable memory, but this takes away 1GB of memory from the kernel which could have worse affects on the entire system such as with Pool Paged Memory and Pool Non-Paged Memory.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\Process(_Total)\Virtual Bytes | 14,033,108,992 | 14,085,652,568 | 15,321,989,120 | -2,616,354,493 | 75,228,326 | 14,074,463,350 | 14,072,244,685 | 14,070,588,587
\\DB04\Process(dfrgifc)\Virtual Bytes | 32,862,208 | 34,293,077 | 35,532,800 | - | 0 | - | - | -
\\DB04\Process(powershell#4)\Virtual Bytes | 555,057,152 | 555,057,152 | 555,057,152 | - | 0 | - | - | -
\\DB04\Process(cmd#4)\Virtual Bytes | 17,014,784 | 17,014,784 | 17,014,784 | - | 0 | - | - | -
\\DB04\Process(powershell#3)\Virtual Bytes | 556,105,728 | 556,105,728 | 556,105,728 | - | 0 | - | - | -
\\DB04\Process(cmd#3)\Virtual Bytes | 17,014,784 | 17,014,784 | 17,014,784 | - | 0 | - | - | -
\\DB04\Process(powershell#2)\Virtual Bytes | 556,105,728 | 559,235,006 | 565,084,160 | 55,076,109 | 2,745,289 | 559,161,029 | 558,910,669 | 559,073,573
\\DB04\Process(cmd#2)\Virtual Bytes | 17,014,784 | 17,014,784 | 17,014,784 | 0 | 0 | 17,014,784 | 17,014,784 | 17,014,784
\\DB04\Process(SQLCMD#1)\Virtual Bytes | 67,067,904 | 67,067,904 | 67,067,904 | - | 0 | - | - | -
\\DB04\Process(SQLCMD)\Virtual Bytes | 67,067,904 | 67,642,930 | 69,165,056 | -13,245,171 | 618,984 | 67,602,274 | 67,605,299 | 67,610,917
\\DB04\Process(msinfo32)\Virtual Bytes | 59,789,312 | 65,206,955 | 66,080,768 | 223,512,253 | 1,055,833 | 65,206,955 | 65,949,696 | 65,949,696
\\DB04\Process(cmd#1)\Virtual Bytes | 17,014,784 | 19,718,937 | 44,957,696 | -176,481,549 | 8,261,323 | 18,089,511 | 17,014,784 | 17,014,784
\\DB04\Process(SQLdiag)\Virtual Bytes | 93,011,968 | 93,546,628 | 94,068,736 | -6,609,651 | 516,001 | 93,568,394 | 93,577,421 | 93,594,185
\\DB04\Process(powershell#1)\Virtual Bytes | 553,938,944 | 554,298,335 | 554,987,520 | -6,622,585 | 418,435 | 554,286,789 | 554,233,856 | 554,182,363
\\DB04\Process(cmd)\Virtual Bytes | 17,018,880 | 17,018,880 | 17,018,880 | 0 | 0 | 17,018,880 | 17,018,880 | 17,018,880
\\DB04\Process(explorer#1)\Virtual Bytes | 109,105,152 | 109,460,315 | 110,153,728 | -6,622,585 | 338,197 | 109,447,956 | 109,439,386 | 109,470,281
\\DB04\Process(svchost#8)\Virtual Bytes | 51,781,632 | 51,781,632 | 51,781,632 | 0 | 0 | 51,781,632 | 51,781,632 | 51,781,632
\\DB04\Process(SQLAGENT)\Virtual Bytes | 531,070,976 | 531,070,976 | 531,070,976 | 0 | 0 | 531,070,976 | 531,070,976 | 531,070,976
\\DB04\Process(fdhost)\Virtual Bytes | 40,017,920 | 40,533,752 | 40,542,208 | 0 | 32,200 | 40,542,208 | 40,542,208 | 40,542,208
\\DB04\Process(sqlservr)\Virtual Bytes | 5,746,880,512 | 5,795,491,488 | 5,817,135,104 | 421,775,899 | 26,133,809 | 5,799,449,416 | 5,804,606,532 | 5,811,010,219
\\DB04\Process(Ssms)\Virtual Bytes | 556,937,216 | 557,772,271 | 558,247,936 | 2,069,558 | 621,945 | 557,832,034 | 557,903,872 | 558,037,285
\\DB04\Process(wpabaln)\Virtual Bytes | 55,492,608 | 55,492,608 | 55,492,608 | 0 | 0 | 55,492,608 | 55,492,608 | 55,492,608
\\DB04\Process(powershell)\Virtual Bytes | 605,962,240 | 605,962,240 | 605,962,240 | 0 | 0 | 605,962,240 | 605,962,240 | 605,962,240
\\DB04\Process(wmiprvse#1)\Virtual Bytes | 40,382,464 | 40,382,464 | 40,382,464 | 0 | 0 | 40,382,464 | 40,382,464 | 40,382,464
\\DB04\Process(explorer)\Virtual Bytes | 123,330,560 | 123,630,757 | 123,854,848 | -3,311,293 | 256,142 | 123,648,158 | 123,664,794 | 123,695,689
\\DB04\Process(wmiprvse)\Virtual Bytes | 155,283,456 | 184,267,853 | 196,575,232 | -49,908,682 | 15,275,838 | 186,396,094 | 188,120,149 | 191,421,928
\\DB04\Process(alg)\Virtual Bytes | 30,244,864 | 30,244,864 | 30,244,864 | 0 | 0 | 30,244,864 | 30,244,864 | 30,244,864
\\DB04\Process(fdlauncher)\Virtual Bytes | 20,078,592 | 20,078,592 | 20,078,592 | 0 | 0 | 20,078,592 | 20,078,592 | 20,078,592
\\DB04\Process(svchost#7)\Virtual Bytes | 72,953,856 | 73,789,616 | 74,002,432 | -3,311,293 | 396,528 | 73,869,680 | 73,969,664 | 74,002,432
\\DB04\Process(sqlwriter)\Virtual Bytes | 37,679,104 | 37,679,104 | 37,679,104 | 0 | 0 | 37,679,104 | 37,679,104 | 37,679,104
\\DB04\Process(svchost#6)\Virtual Bytes | 16,613,376 | 16,613,376 | 16,613,376 | 0 | 0 | 16,613,376 | 16,613,376 | 16,613,376
\\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0 | 0 | 2,822,803,456 | 2,822,803,456 | 2,822,803,456
\\DB04\Process(svchost#5)\Virtual Bytes | 25,645,056 | 25,645,056 | 25,645,056 | 0 | 0 | 25,645,056 | 25,645,056 | 25,645,056
\\DB04\Process(msdtc)\Virtual Bytes | 38,940,672 | 38,940,672 | 38,940,672 | 0 | 0 | 38,940,672 | 38,940,672 | 38,940,672
\\DB04\Process(vmicsvc#4)\Virtual Bytes | 45,465,600 | 45,465,600 | 45,465,600 | 0 | 0 | 45,465,600 | 45,465,600 | 45,465,600
\\DB04\Process(vmicsvc#3)\Virtual Bytes | 42,557,440 | 42,557,440 | 42,557,440 | 0 | 0 | 42,557,440 | 42,557,440 | 42,557,440
\\DB04\Process(vmicsvc#2)\Virtual Bytes | 42,704,896 | 42,704,896 | 42,704,896 | 0 | 0 | 42,704,896 | 42,704,896 | 42,704,896
\\DB04\Process(vmicsvc#1)\Virtual Bytes | 77,250,560 | 77,250,560 | 77,250,560 | 0 | 0 | 77,250,560 | 77,250,560 | 77,250,560
\\DB04\Process(vmicsvc)\Virtual Bytes | 52,248,576 | 52,248,576 | 52,248,576 | 0 | 0 | 52,248,576 | 52,248,576 | 52,248,576
\\DB04\Process(spoolsv)\Virtual Bytes | 58,556,416 | 58,990,504 | 59,080,704 | -3,311,293 | 192,832 | 59,033,653 | 59,080,704 | 59,080,704
\\DB04\Process(svchost#4)\Virtual Bytes | 535,433,216 | 558,153,453 | 580,907,008 | -219,534,821 | 21,029,278 | 559,068,436 | 559,508,326 | 560,431,372
\\DB04\Process(svchost#3)\Virtual Bytes | 40,239,104 | 40,268,701 | 40,763,392 | -3,311,293 | 113,924 | 40,239,104 | 40,239,104 | 40,239,104
\\DB04\Process(svchost#2)\Virtual Bytes | 69,795,840 | 69,795,840 | 69,795,840 | 0 | 0 | 69,795,840 | 69,795,840 | 69,795,840
\\DB04\Process(svchost#1)\Virtual Bytes | 33,902,592 | 34,305,674 | 34,426,880 | 827,823 | 208,711 | 34,342,859 | 34,396,297 | 34,426,880
\\DB04\Process(svchost)\Virtual Bytes | 29,597,696 | 30,031,784 | 30,121,984 | -3,311,293 | 192,832 | 30,074,933 | 30,121,984 | 30,121,984
\\DB04\Process(lsass)\Virtual Bytes | 75,223,040 | 75,785,381 | 76,271,616 | -3,311,293 | 376,944 | 75,812,864 | 75,832,525 | 75,803,502
\\DB04\Process(services)\Virtual Bytes | 318,431,232 | 319,083,245 | 319,545,344 | -5,794,762 | 440,221 | 319,115,369 | 319,143,663 | 319,188,407
\\DB04\Process(winlogon)\Virtual Bytes | 84,213,760 | 84,484,360 | 85,262,336 | -3,311,293 | 384,013 | 84,455,739 | 84,379,785 | 84,338,590
\\DB04\Process(csrss)\Virtual Bytes | 55,136,256 | 55,153,169 | 55,660,544 | -1,655,646 | 55,128 | 55,141,297 | 55,136,256 | 55,136,256
\\DB04\Process(smss)\Virtual Bytes | 5,218,304 | 5,218,304 | 5,218,304 | 0 | 0 | 5,218,304 | 5,218,304 | 5,218,304
\\DB04\Process(System)\Virtual Bytes | 2,490,368 | 2,490,368 | 2,490,368 | 0 | 0 | 2,490,368 | 2,490,368 | 2,490,368
\\DB04\Process(Idle)\Virtual Bytes | 0 | - | 0 | 0 | 0 | - | - | -

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\Process(dfrgifc)\Virtual Bytes | 32,862,208 | 34,293,077 | 35,532,800 | -
* | OK | \\DB04\Process(powershell#4)\Virtual Bytes | 555,057,152 | 555,057,152 | 555,057,152 | -
* | OK | \\DB04\Process(cmd#4)\Virtual Bytes | 17,014,784 | 17,014,784 | 17,014,784 | -
* | OK | \\DB04\Process(powershell#3)\Virtual Bytes | 556,105,728 | 556,105,728 | 556,105,728 | -
* | OK | \\DB04\Process(cmd#3)\Virtual Bytes | 17,014,784 | 17,014,784 | 17,014,784 | -
* | OK | \\DB04\Process(powershell#2)\Virtual Bytes | 556,105,728 | 559,235,006 | 565,084,160 | 55,076,109
* | OK | \\DB04\Process(cmd#2)\Virtual Bytes | 17,014,784 | 17,014,784 | 17,014,784 | 0
* | OK | \\DB04\Process(SQLCMD#1)\Virtual Bytes | 67,067,904 | 67,067,904 | 67,067,904 | -
* | OK | \\DB04\Process(SQLCMD)\Virtual Bytes | 67,067,904 | 67,642,930 | 69,165,056 | -13,245,171
* | OK | \\DB04\Process(msinfo32)\Virtual Bytes | 59,789,312 | 65,206,955 | 66,080,768 | 223,512,253
* | OK | \\DB04\Process(cmd#1)\Virtual Bytes | 17,014,784 | 19,718,937 | 44,957,696 | -176,481,549
* | OK | \\DB04\Process(SQLdiag)\Virtual Bytes | 93,011,968 | 93,546,628 | 94,068,736 | -6,609,651
* | OK | \\DB04\Process(powershell#1)\Virtual Bytes | 553,938,944 | 554,298,335 | 554,987,520 | -6,622,585
* | OK | \\DB04\Process(cmd)\Virtual Bytes | 17,018,880 | 17,018,880 | 17,018,880 | 0
* | OK | \\DB04\Process(explorer#1)\Virtual Bytes | 109,105,152 | 109,460,315 | 110,153,728 | -6,622,585
* | OK | \\DB04\Process(svchost#8)\Virtual Bytes | 51,781,632 | 51,781,632 | 51,781,632 | 0
* | OK | \\DB04\Process(SQLAGENT)\Virtual Bytes | 531,070,976 | 531,070,976 | 531,070,976 | 0
* | OK | \\DB04\Process(fdhost)\Virtual Bytes | 40,017,920 | 40,533,752 | 40,542,208 | 0
* | OK | \\DB04\Process(Ssms)\Virtual Bytes | 556,937,216 | 557,772,271 | 558,247,936 | 2,069,558
* | OK | \\DB04\Process(wpabaln)\Virtual Bytes | 55,492,608 | 55,492,608 | 55,492,608 | 0
* | OK | \\DB04\Process(powershell)\Virtual Bytes | 605,962,240 | 605,962,240 | 605,962,240 | 0
* | OK | \\DB04\Process(wmiprvse#1)\Virtual Bytes | 40,382,464 | 40,382,464 | 40,382,464 | 0
* | OK | \\DB04\Process(explorer)\Virtual Bytes | 123,330,560 | 123,630,757 | 123,854,848 | -3,311,293
* | OK | \\DB04\Process(wmiprvse)\Virtual Bytes | 155,283,456 | 184,267,853 | 196,575,232 | -49,908,682
* | OK | \\DB04\Process(alg)\Virtual Bytes | 30,244,864 | 30,244,864 | 30,244,864 | 0
* | OK | \\DB04\Process(fdlauncher)\Virtual Bytes | 20,078,592 | 20,078,592 | 20,078,592 | 0
* | OK | \\DB04\Process(svchost#7)\Virtual Bytes | 72,953,856 | 73,789,616 | 74,002,432 | -3,311,293
* | OK | \\DB04\Process(sqlwriter)\Virtual Bytes | 37,679,104 | 37,679,104 | 37,679,104 | 0
* | OK | \\DB04\Process(svchost#6)\Virtual Bytes | 16,613,376 | 16,613,376 | 16,613,376 | 0
12/16/2009 1:04:09 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:04:28 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:04:47 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:05:06 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:05:25 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:05:44 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:06:03 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:06:22 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:06:41 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:07:00 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:07:19 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:07:38 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:07:57 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:08:16 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:08:35 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:08:54 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:09:13 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:09:32 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:09:51 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:10:10 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:10:29 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:10:48 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:11:07 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:11:26 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:11:45 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:12:04 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:12:23 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:12:42 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:13:01 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:13:20 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0
12/16/2009 1:13:39 PM | High User-mode Memory Usage - consuming more than 80% of available virtual memory | \\DB04\Process(MsDtsSrvr)\Virtual Bytes | 2,822,803,456 | 2,822,803,456 | 2,822,803,456 | 0

Back to the top

## Process Working Set

> Description: Working Set is the current size, in bytes, of the Working Set of this process. The Working Set is the set of memory pages touched recently by the threads in the process. If free memory in the computer is above a threshold, pages are left in the Working Set of a process even if they are not in use. When free memory falls below a threshold, pages are trimmed from Working Sets. If they are needed they will then be soft-faulted back into the Working Set before leaving main memory.
> This analysis checks for an increasing trend of 10MB’s or more in each of the processes. Use in correlation with Available Memory Analysis.
> References:
> Detecting Memory Bottlenecks http://www.microsoft.com/resources/documentation/windowsnt/4/workstation/reskit/en-us/04memory.mspx?mfr=true

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\Process(_Total)\Working Set | 1,800,110,080 | 1,828,314,398 | 1,951,567,872 | -409,733,659 | 18,355,712 | 1,828,923,143 | 1,831,158,391 | 1,832,915,017
\\DB04\Process(dfrgifc)\Working Set | 4,153,344 | 4,623,019 | 4,857,856 | - | 0 | - | - | -
\\DB04\Process(powershell#4)\Working Set | 48,107,520 | 48,107,520 | 48,107,520 | - | 0 | - | - | -
\\DB04\Process(cmd#4)\Working Set | 2,277,376 | 2,277,376 | 2,277,376 | - | 0 | - | - | -
\\DB04\Process(powershell#3)\Working Set | 45,703,168 | 45,703,168 | 45,703,168 | - | 0 | - | - | -
\\DB04\Process(cmd#3)\Working Set | 2,273,280 | 2,273,280 | 2,273,280 | - | 0 | - | - | -
\\DB04\Process(powershell#2)\Working Set | 47,104,000 | 49,984,336 | 52,613,120 | 23,528,286 | 1,482,755 | 50,090,102 | 50,108,672 | 50,115,511
\\DB04\Process(cmd#2)\Working Set | 2,281,472 | 2,281,472 | 2,281,472 | 0 | 0 | 2,281,472 | 2,281,472 | 2,281,472
\\DB04\Process(SQLCMD#1)\Working Set | 9,633,792 | 9,633,792 | 9,633,792 | - | 0 | - | - | -
\\DB04\Process(SQLCMD)\Working Set | 10,170,368 | 10,218,430 | 10,235,904 | 116,413 | 13,866 | 10,220,150 | 10,221,261 | 10,223,616
\\DB04\Process(msinfo32)\Working Set | 8,048,640 | 11,620,352 | 13,139,968 | 267,264,000 | 1,198,712 | 11,620,352 | 12,443,136 | 12,443,136
\\DB04\Process(cmd#1)\Working Set | 2,281,472 | 2,634,653 | 5,931,008 | -23,049,701 | 1,078,985 | 2,421,839 | 2,281,472 | 2,281,472
\\DB04\Process(SQLdiag)\Working Set | 22,011,904 | 22,272,881 | 22,339,584 | 1,047,714 | 55,093 | 22,276,372 | 22,275,209 | 22,272,878
\\DB04\Process(powershell#1)\Working Set | 47,366,144 | 47,376,483 | 47,394,816 | -129,347 | 8,776 | 47,376,463 | 47,375,258 | 47,373,897
\\DB04\Process(cmd)\Working Set | 2,478,080 | 2,478,080 | 2,478,080 | 0 | 0 | 2,478,080 | 2,478,080 | 2,478,080
\\DB04\Process(explorer#1)\Working Set | 17,530,880 | 17,543,300 | 17,580,032 | -232,825 | 13,504 | 17,541,908 | 17,541,325 | 17,542,290
\\DB04\Process(svchost#8)\Working Set | 1,703,936 | 1,703,936 | 1,703,936 | 0 | 0 | 1,703,936 | 1,703,936 | 1,703,936
\\DB04\Process(SQLAGENT)\Working Set | 8,118,272 | 8,245,116 | 8,249,344 | 827,823 | 23,158 | 8,249,344 | 8,249,344 | 8,249,344
\\DB04\Process(fdhost)\Working Set | 1,073,152 | 1,089,272 | 1,089,536 | 0 | 1,006 | 1,089,536 | 1,089,536 | 1,089,536
\\DB04\Process(sqlservr)\Working Set | 1,335,029,760 | 1,360,767,494 | 1,375,408,128 | -114,013,238 | 16,513,618 | 1,362,614,180 | 1,364,780,868 | 1,367,059,212
\\DB04\Process(Ssms)\Working Set | 136,318,976 | 136,401,458 | 136,445,952 | 666,139 | 50,219 | 136,407,552 | 136,415,078 | 136,422,254
\\DB04\Process(wpabaln)\Working Set | 413,696 | 413,696 | 413,696 | 0 | 0 | 413,696 | 413,696 | 413,696
\\DB04\Process(powershell)\Working Set | 25,821,184 | 25,821,184 | 25,821,184 | 0 | 0 | 25,821,184 | 25,821,184 | 25,821,184
\\DB04\Process(wmiprvse#1)\Working Set | 806,912 | 806,912 | 806,912 | 0 | 0 | 806,912 | 806,912 | 806,912
\\DB04\Process(explorer)\Working Set | 11,694,080 | 11,703,461 | 11,710,464 | -103,478 | 8,004 | 11,704,005 | 11,704,525 | 11,705,490
\\DB04\Process(wmiprvse)\Working Set | 45,064,192 | 55,399,589 | 58,576,896 | -17,157,928 | 1,808,147 | 55,674,644 | 55,865,139 | 56,214,065
\\DB04\Process(alg)\Working Set | 466,944 | 466,944 | 466,944 | 0 | 0 | 466,944 | 466,944 | 466,944
\\DB04\Process(fdlauncher)\Working Set | 397,312 | 397,312 | 397,312 | 0 | 0 | 397,312 | 397,312 | 397,312
\\DB04\Process(svchost#7)\Working Set | 2,613,248 | 2,642,713 | 2,650,112 | -129,347 | 13,897 | 2,645,543 | 2,649,088 | 2,650,112
\\DB04\Process(sqlwriter)\Working Set | 569,344 | 569,344 | 569,344 | 0 | 0 | 569,344 | 569,344 | 569,344
\\DB04\Process(svchost#6)\Working Set | 380,928 | 380,928 | 380,928 | 0 | 0 | 380,928 | 380,928 | 380,928
\\DB04\Process(MsDtsSrvr)\Working Set | 3,452,928 | 3,452,928 | 3,452,928 | 0 | 0 | 3,452,928 | 3,452,928 | 3,452,928
\\DB04\Process(svchost#5)\Working Set | 307,200 | 307,200 | 307,200 | 0 | 0 | 307,200 | 307,200 | 307,200
\\DB04\Process(msdtc)\Working Set | 577,536 | 577,536 | 577,536 | 0 | 0 | 577,536 | 577,536 | 577,536
\\DB04\Process(vmicsvc#4)\Working Set | 577,536 | 577,536 | 577,536 | 0 | 0 | 577,536 | 577,536 | 577,536
\\DB04\Process(vmicsvc#3)\Working Set | 733,184 | 733,184 | 733,184 | 0 | 0 | 733,184 | 733,184 | 733,184
\\DB04\Process(vmicsvc#2)\Working Set | 495,616 | 495,616 | 495,616 | 0 | 0 | 495,616 | 495,616 | 495,616
\\DB04\Process(vmicsvc#1)\Working Set | 716,800 | 716,800 | 716,800 | 0 | 0 | 716,800 | 716,800 | 716,800
\\DB04\Process(vmicsvc)\Working Set | 872,448 | 872,448 | 872,448 | 0 | 0 | 872,448 | 872,448 | 872,448
\\DB04\Process(spoolsv)\Working Set | 1,839,104 | 1,872,885 | 1,880,064 | -232,825 | 15,021 | 1,876,231 | 1,879,859 | 1,880,064
\\DB04\Process(svchost#4)\Working Set | 23,797,760 | 24,899,463 | 29,315,072 | -9,739,857 | 797,717 | 24,915,364 | 24,920,252 | 24,922,673
\\DB04\Process(svchost#3)\Working Set | 1,892,352 | 1,893,277 | 1,908,736 | -103,478 | 3,560 | 1,892,352 | 1,892,352 | 1,892,352
\\DB04\Process(svchost#2)\Working Set | 2,138,112 | 2,140,931 | 2,146,304 | 51,739 | 3,829 | 2,140,843 | 2,140,433 | 2,139,672
\\DB04\Process(svchost#1)\Working Set | 2,330,624 | 2,345,731 | 2,355,200 | -12,935 | 8,471 | 2,346,745 | 2,347,895 | 2,347,301
\\DB04\Process(svchost)\Working Set | 1,650,688 | 1,671,036 | 1,675,264 | -155,217 | 9,039 | 1,673,058 | 1,675,264 | 1,675,264
\\DB04\Process(lsass)\Working Set | 8,269,824 | 8,383,543 | 8,417,280 | 743,747 | 28,246 | 8,388,542 | 8,387,908 | 8,388,852
\\DB04\Process(services)\Working Set | 4,775,936 | 5,313,184 | 5,857,280 | -1,416,354 | 264,544 | 5,290,050 | 5,228,015 | 5,180,709
\\DB04\Process(winlogon)\Working Set | 6,717,440 | 6,725,896 | 6,750,208 | -103,478 | 12,000 | 6,725,002 | 6,722,628 | 6,721,341
\\DB04\Process(csrss)\Working Set | 3,198,976 | 3,202,147 | 3,297,280 | -310,434 | 10,337 | 3,199,921 | 3,198,976 | 3,198,976
\\DB04\Process(smss)\Working Set | 204,800 | 204,800 | 204,800 | 0 | 0 | 204,800 | 204,800 | 204,800
\\DB04\Process(System)\Working Set | 258,048 | 258,048 | 258,048 | 0 | 0 | 258,048 | 258,048 | 258,048
\\DB04\Process(Idle)\Working Set | 24,576 | 24,576 | 24,576 | 0 | 0 | 24,576 | 24,576 | 24,576

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\Process(_Total)\Working Set | 1,800,110,080 | 1,828,314,398 | 1,951,567,872 | -409,733,659
* | OK | \\DB04\Process(dfrgifc)\Working Set | 4,153,344 | 4,623,019 | 4,857,856 | -
* | OK | \\DB04\Process(powershell#4)\Working Set | 48,107,520 | 48,107,520 | 48,107,520 | -
* | OK | \\DB04\Process(cmd#4)\Working Set | 2,277,376 | 2,277,376 | 2,277,376 | -
* | OK | \\DB04\Process(powershell#3)\Working Set | 45,703,168 | 45,703,168 | 45,703,168 | -
* | OK | \\DB04\Process(cmd#3)\Working Set | 2,273,280 | 2,273,280 | 2,273,280 | -
* | OK | \\DB04\Process(powershell#2)\Working Set | 47,104,000 | 49,984,336 | 52,613,120 | 23,528,286
* | OK | \\DB04\Process(cmd#2)\Working Set | 2,281,472 | 2,281,472 | 2,281,472 | 0
* | OK | \\DB04\Process(SQLCMD#1)\Working Set | 9,633,792 | 9,633,792 | 9,633,792 | -
* | OK | \\DB04\Process(SQLCMD)\Working Set | 10,170,368 | 10,218,430 | 10,235,904 | 116,413
* | OK | \\DB04\Process(msinfo32)\Working Set | 8,048,640 | 11,620,352 | 13,139,968 | 267,264,000
* | OK | \\DB04\Process(cmd#1)\Working Set | 2,281,472 | 2,634,653 | 5,931,008 | -23,049,701
* | OK | \\DB04\Process(SQLdiag)\Working Set | 22,011,904 | 22,272,881 | 22,339,584 | 1,047,714
* | OK | \\DB04\Process(powershell#1)\Working Set | 47,366,144 | 47,376,483 | 47,394,816 | -129,347
* | OK | \\DB04\Process(cmd)\Working Set | 2,478,080 | 2,478,080 | 2,478,080 | 0
* | OK | \\DB04\Process(explorer#1)\Working Set | 17,530,880 | 17,543,300 | 17,580,032 | -232,825
* | OK | \\DB04\Process(svchost#8)\Working Set | 1,703,936 | 1,703,936 | 1,703,936 | 0
* | OK | \\DB04\Process(SQLAGENT)\Working Set | 8,118,272 | 8,245,116 | 8,249,344 | 827,823
* | OK | \\DB04\Process(fdhost)\Working Set | 1,073,152 | 1,089,272 | 1,089,536 | 0
* | OK | \\DB04\Process(sqlservr)\Working Set | 1,335,029,760 | 1,360,767,494 | 1,375,408,128 | -114,013,238
* | OK | \\DB04\Process(Ssms)\Working Set | 136,318,976 | 136,401,458 | 136,445,952 | 666,139
* | OK | \\DB04\Process(wpabaln)\Working Set | 413,696 | 413,696 | 413,696 | 0
* | OK | \\DB04\Process(powershell)\Working Set | 25,821,184 | 25,821,184 | 25,821,184 | 0
* | OK | \\DB04\Process(wmiprvse#1)\Working Set | 806,912 | 806,912 | 806,912 | 0
* | OK | \\DB04\Process(explorer)\Working Set | 11,694,080 | 11,703,461 | 11,710,464 | -103,478
* | OK | \\DB04\Process(wmiprvse)\Working Set | 45,064,192 | 55,399,589 | 58,576,896 | -17,157,928
* | OK | \\DB04\Process(alg)\Working Set | 466,944 | 466,944 | 466,944 | 0
* | OK | \\DB04\Process(fdlauncher)\Working Set | 397,312 | 397,312 | 397,312 | 0
* | OK | \\DB04\Process(svchost#7)\Working Set | 2,613,248 | 2,642,713 | 2,650,112 | -129,347
* | OK | \\DB04\Process(sqlwriter)\Working Set | 569,344 | 569,344 | 569,344 | 0
* | OK | \\DB04\Process(svchost#6)\Working Set | 380,928 | 380,928 | 380,928 | 0
* | OK | \\DB04\Process(MsDtsSrvr)\Working Set | 3,452,928 | 3,452,928 | 3,452,928 | 0
* | OK | \\DB04\Process(svchost#5)\Working Set | 307,200 | 307,200 | 307,200 | 0
* | OK | \\DB04\Process(msdtc)\Working Set | 577,536 | 577,536 | 577,536 | 0
* | OK | \\DB04\Process(vmicsvc#4)\Working Set | 577,536 | 577,536 | 577,536 | 0
* | OK | \\DB04\Process(vmicsvc#3)\Working Set | 733,184 | 733,184 | 733,184 | 0
* | OK | \\DB04\Process(vmicsvc#2)\Working Set | 495,616 | 495,616 | 495,616 | 0
* | OK | \\DB04\Process(vmicsvc#1)\Working Set | 716,800 | 716,800 | 716,800 | 0
* | OK | \\DB04\Process(vmicsvc)\Working Set | 872,448 | 872,448 | 872,448 | 0
* | OK | \\DB04\Process(spoolsv)\Working Set | 1,839,104 | 1,872,885 | 1,880,064 | -232,825
* | OK | \\DB04\Process(svchost#4)\Working Set | 23,797,760 | 24,899,463 | 29,315,072 | -9,739,857
* | OK | \\DB04\Process(svchost#3)\Working Set | 1,892,352 | 1,893,277 | 1,908,736 | -103,478
* | OK | \\DB04\Process(svchost#2)\Working Set | 2,138,112 | 2,140,931 | 2,146,304 | 51,739
* | OK | \\DB04\Process(svchost#1)\Working Set | 2,330,624 | 2,345,731 | 2,355,200 | -12,935
* | OK | \\DB04\Process(svchost)\Working Set | 1,650,688 | 1,671,036 | 1,675,264 | -155,217
* | OK | \\DB04\Process(lsass)\Working Set | 8,269,824 | 8,383,543 | 8,417,280 | 743,747
* | OK | \\DB04\Process(services)\Working Set | 4,775,936 | 5,313,184 | 5,857,280 | -1,416,354
* | OK | \\DB04\Process(winlogon)\Working Set | 6,717,440 | 6,725,896 | 6,750,208 | -103,478
* | OK | \\DB04\Process(csrss)\Working Set | 3,198,976 | 3,202,147 | 3,297,280 | -310,434
* | OK | \\DB04\Process(smss)\Working Set | 204,800 | 204,800 | 204,800 | 0
* | OK | \\DB04\Process(System)\Working Set | 258,048 | 258,048 | 258,048 | 0
* | OK | \\DB04\Process(Idle)\Working Set | 24,576 | 24,576 | 24,576 | 0

Back to the top

## Memory System Cache Resident Bytes

> Description: System Cache Resident Bytes is the size, in bytes, of the pageable operating system code in the file system cache. This value includes only current physical pages and does not include any virtual memory pages not currently resident. It does equal the System Cache value shown in Task Manager. As a result, this value may be smaller than the actual amount of virtual memory in use by the file system cache. This value is a component of Memory\\System Code Resident Bytes which represents all pageable operating system code that is currently in physical memory. This counter displays the last observed value only; it is not an average.
> This analysis checks for an increasing trend of 10MB’s per hour. Under load, a server might use the System Cache in order to cache I/O activity such as disk. Use in correlation with Process IO Data Operations/sec and Process IO Other Operations/sec Analyses.
> References:
> File Cache Performance and Tuning http://technet.microsoft.com/en-us/library/bb742613.aspx

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\Memory\System Cache Resident Bytes | 26,169,344 | 26,655,414 | 27,475,968 | -549,726 | 288,781 | 26,640,804 | 26,616,098 | 26,608,713

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
12/16/2009 1:05:06 PM | Increasing trend of more than 10MB's per hour detected | \\DB04\Memory\System Cache Resident Bytes | 26,796,032 | 26,846,208 | 26,943,488 | 21,212,968.4210526
12/16/2009 1:05:25 PM | Increasing trend of more than 10MB's per hour detected | \\DB04\Memory\System Cache Resident Bytes | 26,357,760 | 26,733,568 | 26,865,664 | 10,574,147.3684211
12/16/2009 1:07:19 PM | Increasing trend of more than 10MB's per hour detected | \\DB04\Memory\System Cache Resident Bytes | 27,045,888 | 27,096,064 | 27,156,480 | 11,098,004.2105263
12/16/2009 1:07:38 PM | Increasing trend of more than 10MB's per hour detected | \\DB04\Memory\System Cache Resident Bytes | 27,172,864 | 27,215,189 | 27,254,784 | 12,141,014.354067
12/16/2009 1:07:57 PM | Increasing trend of more than 10MB's per hour detected | \\DB04\Memory\System Cache Resident Bytes | 27,271,168 | 27,334,656 | 27,394,048 | 13,015,578.9473684
12/16/2009 1:08:16 PM | Increasing trend of more than 10MB's per hour detected | \\DB04\Memory\System Cache Resident Bytes | 27,426,816 | 27,453,440 | 27,475,968 | 13,745,645.3441296

Back to the top

## Memory Pages Input/sec

> Description: Pages Input/sec is the rate at which pages are read from disk to resolve hard page faults. Hard page faults occur when a process refers to a page in virtual memory that is not in its working set or elsewhere in physical memory, and must be retrieved from disk. When a page is faulted, the system tries to read multiple contiguous pages into memory to maximize the benefit of the read operation. Compare the value of Memory\\Pages Input/sec to the value of Memory\\Page Reads/sec to determine the average number of pages read into memory during each read operation.
> Reference:
> How to determine the appropriate page file size for 64-bit versions of Windows Server 2003 or Windows XP
> http://support.microsoft.com/kb/889654

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\Memory\Pages Input/sec | 0 | 13 | 259 | -1,204 | 42 | 2 | 0 | 0

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
12/16/2009 1:04:09 PM | More then 10 page file reads per second | \\DB04\Memory\Pages Input/sec | 116 | 191 | 244 | 0
12/16/2009 1:04:28 PM | More then 10 page file reads per second | \\DB04\Memory\Pages Input/sec | 35 | 149 | 259 | -7,949
12/16/2009 1:04:47 PM | More then 10 page file reads per second | \\DB04\Memory\Pages Input/sec | 0 | 9 | 26 | -17,168
12/16/2009 1:05:06 PM | More then 10 page file reads per second | \\DB04\Memory\Pages Input/sec | 0 | 33 | 132 | -9,930

Back to the top

## Memory Percent Committed Bytes In Use

> Description: % Committed Bytes In Use is the ratio of Memory\\Committed Bytes to the Memory\\Commit Limit. Committed memory is the physical memory in use for which space has been reserved in the paging file should it need to be written to disk. The commit limit is determined by the size of the paging file. If the paging file is enlarged, the commit limit increases, and the ratio is reduced). This counter displays the current percentage value only; it is not an average.
> This analysis checks if the amount of Commited memory is becoming close to the Commit Limit (RAM plus total page file sizes), If so, then identify if you have a memory leak. If no memory leak is identified, then consider adding more physical RAM or increase the size of your page files.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\Memory\% Committed Bytes In Use | 53 | 55 | 57 | -1 | 1 | 55 | 55 | 55

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\Memory\% Committed Bytes In Use | 53 | 55 | 57 | -1

Back to the top

# SQL Server Process

## Process % Privileged Time

> Description: % Privileged Time is the percentage of elapsed time that the process threads spent executing code in privileged mode. When a Windows system service is called, the service will often run in privileged mode to gain access to system-private data. Such data is protected from access by threads executing in user mode. Calls to the system can be explicit or implicit, such as page faults or interrupts. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. Some work done by Windows on behalf of the application might appear in other subsystem processes in addition to the privileged time in the process.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\Process(sqlservr)\% Privileged Time | 0 | 1 | 4 | 9 | 1 | 1 | 1 | 1

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\Process(sqlservr)\% Privileged Time | 0 | 1 | 4 | 9

Back to the top

# SQLServer:Access Methods

## SQLServer:Access Methods Forwarded Records/sec

> Description: Rows with varchar columns can experience expansion when varchar values are updated with a longer string. In the case where the row cannot fit in the existing page, the row migrates and access to the row will traverse a pointer. This only happens on heaps (tables without clustered indexes). Recommendations include: Evaluate clustered index for heap tables. Consider using default values or char instead of varchar. In cases where clustered indexes cannot be used, drop non-clustered indexes, build a clustered index to reorg pages and rows, drop the clustered index, then recreate non-clustered indexes.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:Access Methods\Forwarded Records/sec | 0 | - | 0 | 0 | 0 | - | - | -

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\SQLServer:Access Methods\Forwarded Records/sec | 0 | - | 0 | 0

Back to the top

## SQLServer:Access Methods FreeSpace Scans/sec

> Description: Inserts into heaps will require SQL Server to perform freespace scans to identify pages with free space to insert rows. Freespace scans are additional I/O expense for inserts and can possibly cause contention on the GAM, SGAM, and PFS pages when many spids are inserting. Evaluate clustered index for base tables.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:Access Methods\FreeSpace Scans/sec | 0 | 9 | 742 | -1,561 | 44 | 0 | 0 | 0

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
12/16/2009 1:04:09 PM | > 10% of the number of Batch Requests/Sec | \\DB04\SQLServer:Access Methods\FreeSpace Scans/sec | 0 | 247 | 742 | 0
12/16/2009 1:04:47 PM | > 10% of the number of Batch Requests/Sec | \\DB04\SQLServer:Access Methods\FreeSpace Scans/sec | 0 | 41 | 115 | -19,511

Back to the top

## SQLServer:Access Methods Full Scans/sec

> Description: 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.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 5 | 22 | 99 | 4 | 4 | 4 | 4

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
12/16/2009 1:04:28 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 1 | 2 | 3 | 221
12/16/2009 1:04:47 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 2 | 4 | 8 | 314
12/16/2009 1:05:06 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 1 | 1 | -22
12/16/2009 1:05:25 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 1 | 1 | -19
12/16/2009 1:05:44 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 1 | 1 | -15
12/16/2009 1:06:03 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 1 | 1 | -11
12/16/2009 1:06:22 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 0 | 1 | -18
12/16/2009 1:06:41 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 4 | 15 | 21 | 319
12/16/2009 1:07:00 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 12 | 15 | 19 | 293
12/16/2009 1:07:19 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 12 | 15 | 18 | 271
12/16/2009 1:07:38 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 7 | 9 | 13 | 142
12/16/2009 1:07:57 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 4 | 8 | 48
12/16/2009 1:08:16 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 2 | 6 | 21
12/16/2009 1:08:35 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 1 | 4 | 8 | 43
12/16/2009 1:08:54 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 4 | 8 | 39
12/16/2009 1:09:13 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 3 | 9 | 21
12/16/2009 1:09:32 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 4 | 8 | 35
12/16/2009 1:09:51 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 1 | 3 | 7 | 23
12/16/2009 1:10:10 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 3 | 9 | 24
12/16/2009 1:10:29 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 6 | 8 | 42
12/16/2009 1:10:48 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 2 | 8 | 12
12/16/2009 1:11:07 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 1 | 4 | 7 | 27
12/16/2009 1:11:26 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 4 | 9 | 26
12/16/2009 1:11:45 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 2 | 6 | 11
12/16/2009 1:12:04 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 1 | 5 | 8 | 32
12/16/2009 1:12:23 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 2 | 8 | 10
12/16/2009 1:12:42 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 0 | 4 | 9 | 22
12/16/2009 1:13:01 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 1 | 4 | 8 | 22
12/16/2009 1:13:20 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 1 | 3 | 7 | 13
12/16/2009 1:13:39 PM | Ratio of Index searches/sec to Full scan/sec < 1000 to 1. | \\DB04\SQLServer:Access Methods\Full Scans/sec | 12 | 17 | 22 | 99

Back to the top

## SQLServer:Access Methods Page Splits/sec

> Description: Number of page splits per second that occur as the result of overflowing index pages. Dependent upon table/index design. This value needs to be low as possible. Heavily fragmented indexes may be the result of high page splits/sec Recommendation: If the number of page splits is high, consider increasing the fillfactor of your indexes. An increased fillfactor helps to reduce page splits by increasing the amount of free space on each page. Note: This counter also includes new page allocations, and doesn’t mean there is an issue.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:Access Methods\Page Splits/sec | 0 | 1 | 4 | -6 | 0 | 1 | 1 | 1

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\SQLServer:Access Methods\Page Splits/sec | 0 | 1 | 4 | -6

Back to the top

## SQLServer:Access Methods Scan Point Revalidations/sec

> Description: Number of times per second that the scan point had to be revalidated to continue the scan. If a page latch has to be released, due to contention, the scan point must be revalidated when the scan resumes. This can indicate hot spots in the data. Correlate this data with the range scans/sec counter. The higher the number of range scans on the same pages, the higher the number of scan point revalidations.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:Access Methods\Scan Point Revalidations/sec | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\SQLServer:Access Methods\Scan Point Revalidations/sec | 0 | 0 | 1 | 0

Back to the top

## SQLServer:Access Methods Workfiles Created/sec

> Description: Number of workfiles created in the last second. Tempdb workfiles are used in processing hash operations when the amount of data being processed is too big to fit into the available memory. Recommendations: Make queries more efficient by adding/changing indexes, adding additional memory, etc.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:Access Methods\Workfiles Created/sec | 0 | 2 | 32 | -2 | 2 | 1 | 1 | 1

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
12/16/2009 1:04:28 PM | More than 20 Workfiles created per second for every 100 Batch Requests | \\DB04\SQLServer:Access Methods\Workfiles Created/sec | 5 | 13 | 32 | 2,346

Back to the top

## SQLServer:Access Methods Worktables Created/sec

> Description: Number of worktables created in the last second. Tempdb workfiles are used in processing hash operations when the amount of data being processed is too big to fit into the available memory. You may be able to reduce this number by making the queries more efficient by adding/changing indexes, adding additional memory, etc.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:Access Methods\Worktables Created/sec | 0 | 3 | 14 | 55 | 3 | 3 | 2 | 2

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\SQLServer:Access Methods\Worktables Created/sec | 0 | 3 | 14 | 55

Back to the top

## SQLServer:Access Methods Index Searches/sec

> Description: Number of index searches. Index searches are used to start range scans, single index record fetches, and to reposition within an index. Index searches are preferable to index and table scans. For OLTP applications, optimize for more index searches and less scans (preferably, 1 full scan for every 1000 index searches). Index and table scans are expensive I/O operations.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:Access Methods\Index Searches/sec | 0 | 237 | 2,923 | -5,794 | 350 | 168 | 149 | 150

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\SQLServer:Access Methods\Index Searches/sec | 0 | 237 | 2,923 | -5,794

Back to the top

# SQLServer:Buffer Manager

## SQLServer:Buffer Manager Buffer cache hit ratio

> Description: 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.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:Buffer Manager\Buffer cache hit ratio | 97 | 100 | 100 | -11 | 0 | 100 | 100 | 100

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\SQLServer:Buffer Manager\Buffer cache hit ratio | 97 | 100 | 100 | -11

Back to the top

## SQLServer:Buffer Manager Free pages

> Description: Total number of pages on all free lists.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:Buffer Manager\Free pages | 25 | 2,355 | 12,795 | -62,113 | 3,440 | 2,019 | 1,523 | 625

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
12/16/2009 1:07:00 PM | Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 36 | 630 | 1,229 | -197,626
12/16/2009 1:07:19 PM | Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 165 | 286 | 417 | -184,372
12/16/2009 1:07:38 PM | Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 139 | 186 | 250 | -169,332
12/16/2009 1:07:57 PM | Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 104 | 121 | 127 | -156,257
12/16/2009 1:08:16 PM | Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 111 | 157 | 251 | -143,705
12/16/2009 1:08:35 PM | Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 25 | 154 | 241 | -133,488
12/16/2009 1:08:54 PM | Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 180 | 204 | 237 | -123,954
12/16/2009 1:09:13 PM | Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 140 | 209 | 306 | -116,143
12/16/2009 1:09:32 PM | Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 147 | 185 | 238 | -109,580
12/16/2009 1:09:51 PM | Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 123 | 208 | 385 | -103,253
12/16/2009 1:10:10 PM | Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 128 | 177 | 248 | -98,125
12/16/2009 1:10:29 PM | Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 90 | 180 | 268 | -93,196
12/16/2009 1:10:48 PM | Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 144 | 188 | 231 | -88,687
12/16/2009 1:11:07 PM | Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 160 | 215 | 372 | -84,421
12/16/2009 1:11:26 PM | Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 115 | 169 | 255 | -81,130
12/16/2009 1:11:45 PM | Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 72 | 134 | 203 | -78,022
12/16/2009 1:12:04 PM | Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 163 | 208 | 255 | -74,339
12/16/2009 1:12:23 PM | Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 128 | 166 | 184 | -71,790
12/16/2009 1:12:42 PM | Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 101 | 227 | 379 | -68,704
12/16/2009 1:13:01 PM | Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 92 | 178 | 231 | -66,581
12/16/2009 1:13:20 PM | Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 66 | 198 | 400 | -64,155
12/16/2009 1:13:39 PM | Free Pages < 640 | \\DB04\SQLServer:Buffer Manager\Free pages | 148 | 182 | 217 | -62,113

Back to the top

## SQLServer:Buffer Manager Lazy writes/sec

> Description: Number of buffers written by buffer manager's lazy writer. This counter tracks how many times a second that the Lazy Writer process is moving dirty pages from the buffer to disk in order to free up buffer space. Generally speaking, this should not be a high value, say more than 20 per second or so. Ideally, it should be close to zero. If it is zero, this indicates that your SQL Server's buffer cache is plenty big and SQL Server doesn't have to free up dirty pages, instead waiting for this to occur during regular checkpoints. If this value is high, then a need for more memory is indicated.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:Buffer Manager\Lazy writes/sec | 0 | 2 | 65 | 8 | 8 | 0 | 0 | 0

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
12/16/2009 1:10:10 PM | Lazy Writes/second > 20 | \\DB04\SQLServer:Buffer Manager\Lazy writes/sec | 32 | 43 | 56 | 426
12/16/2009 1:10:29 PM | Lazy Writes/second > 20 | \\DB04\SQLServer:Buffer Manager\Lazy writes/sec | 0 | 22 | 65 | 205

Back to the top

## SQLServer:Buffer Manager Page life expectancy

> Description: Number of seconds a page will stay in the buffer pool without references. This performance monitor counter tells you, on average, how long data pages are staying in the buffer. If this value gets below 300 seconds, this is a potential indication that your SQL Server could use more memory in order to boost performance.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:Buffer Manager\Page life expectancy | 18 | 98 | 221 | 156 | 59 | 95 | 86 | 76

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
12/16/2009 1:04:09 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 18 | 26 | 34 | 0
12/16/2009 1:04:28 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 39 | 47 | 55 | 3,932
12/16/2009 1:04:47 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 60 | 65 | 70 | 3,671
12/16/2009 1:05:06 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 75 | 82 | 90 | 3,553
12/16/2009 1:05:25 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 95 | 102 | 110 | 3,612
12/16/2009 1:05:44 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 115 | 123 | 130 | 3,657
12/16/2009 1:06:03 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 135 | 143 | 151 | 3,687
12/16/2009 1:06:22 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 156 | 161 | 166 | 3,647
12/16/2009 1:06:41 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 171 | 178 | 186 | 3,594
12/16/2009 1:07:00 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 191 | 198 | 206 | 3,621
12/16/2009 1:07:19 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 210 | 217 | 221 | 3,614
12/16/2009 1:07:38 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 221 | 221 | 221 | 3,355
12/16/2009 1:07:57 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 221 | 221 | 221 | 3,075
12/16/2009 1:08:16 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 59 | 180 | 221 | 2,248
12/16/2009 1:08:35 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 59 | 59 | 59 | 443
12/16/2009 1:08:54 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 59 | 59 | 59 | 414
12/16/2009 1:09:13 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 44 | 44 | 44 | 210
12/16/2009 1:09:32 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 44 | 44 | 44 | 198
12/16/2009 1:09:51 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 44 | 46 | 50 | 208
12/16/2009 1:10:10 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 56 | 64 | 71 | 371
12/16/2009 1:10:29 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 76 | 79 | 80 | 497
12/16/2009 1:10:48 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 80 | 80 | 80 | 485
12/16/2009 1:11:07 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 80 | 80 | 80 | 463
12/16/2009 1:11:26 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 64 | 76 | 80 | 410
12/16/2009 1:11:45 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 64 | 64 | 64 | 298
12/16/2009 1:12:04 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 64 | 64 | 64 | 286
12/16/2009 1:12:23 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 64 | 64 | 64 | 275
12/16/2009 1:12:42 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 62 | 62 | 64 | 254
12/16/2009 1:13:01 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 62 | 62 | 62 | 242
12/16/2009 1:13:20 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 62 | 62 | 62 | 234
12/16/2009 1:13:39 PM | Page Life Expectancy < 300 seconds | \\DB04\SQLServer:Buffer Manager\Page life expectancy | 51 | 51 | 51 | 156

Back to the top

## SQLServer:Buffer Manager Page lookups/sec

> Description: Number of requests to find a page in the buffer pool. Number of requests to find a page in the buffer pool. When the ratio of page lookups to batch requests is 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.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:Buffer Manager\Page lookups/sec | 0 | 18,401 | 139,019 | 493,887 | 32,238 | 14,183 | 6,442 | 2,641

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
12/16/2009 1:04:09 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 395 | 12,661 | 32,697 | 0
12/16/2009 1:04:28 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 16,546 | 34,538 | 50,124 | 4,145,035
12/16/2009 1:04:47 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 23,631 | 37,231 | 44,666 | 2,327,696
12/16/2009 1:05:06 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 0 | 197 | 494 | -787,200
12/16/2009 1:05:25 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 0 | 149 | 294 | -592,692
12/16/2009 1:06:03 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 0 | 166 | 347 | -394,597
12/16/2009 1:06:22 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2 | 105 | 281 | -339,882
12/16/2009 1:06:41 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 8,966 | 91,029 | 139,019 | 1,856,080
12/16/2009 1:07:00 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 80,318 | 101,723 | 115,169 | 1,874,984
12/16/2009 1:07:19 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 88,460 | 99,527 | 107,960 | 1,645,870
12/16/2009 1:07:38 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 8,165 | 55,304 | 105,712 | 734,517
12/16/2009 1:07:57 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,069 | 2,618 | 3,159 | -158,583
12/16/2009 1:08:16 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,150 | 2,427 | 2,809 | -149,170
12/16/2009 1:08:35 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,128 | 2,587 | 3,082 | -136,340
12/16/2009 1:08:54 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,216 | 2,673 | 3,177 | -126,162
12/16/2009 1:09:13 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,117 | 2,370 | 2,707 | -121,876
12/16/2009 1:09:32 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,367 | 2,657 | 2,974 | -111,499
12/16/2009 1:09:51 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,352 | 2,559 | 2,953 | -106,338
12/16/2009 1:10:10 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,124 | 2,590 | 3,059 | -100,439
12/16/2009 1:10:29 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 1,712 | 2,569 | 3,373 | -95,613
12/16/2009 1:10:48 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,353 | 2,620 | 2,917 | -90,600
12/16/2009 1:11:07 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,525 | 2,730 | 3,024 | -85,533
12/16/2009 1:11:26 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,126 | 2,489 | 3,168 | -83,802
12/16/2009 1:11:45 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,294 | 2,518 | 2,983 | -80,080
12/16/2009 1:12:04 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,408 | 2,733 | 2,960 | -75,243
12/16/2009 1:12:23 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,139 | 2,560 | 3,214 | -73,613
12/16/2009 1:12:42 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 1,732 | 2,631 | 3,402 | -70,385
12/16/2009 1:13:01 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,351 | 2,737 | 3,060 | -67,158
12/16/2009 1:13:20 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 2,457 | 2,715 | 2,888 | -64,984
12/16/2009 1:13:39 PM | Ratio of Page Lookups/sec to Batch Requests/sec < 100 to 1. | \\DB04\SQLServer:Buffer Manager\Page lookups/sec | 75,778 | 90,860 | 105,942 | 493,887

Back to the top

## SQLServer:Buffer Manager Page reads/sec

> Description: Number of physical database page reads issued. Number of physical database page reads issued. 80 – 90 per second is normal, anything that is above indicates indexing or memory constraint.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:Buffer Manager\Page reads/sec | 0 | 480 | 7,509 | 23,584 | 652 | 405 | 433 | 476

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
12/16/2009 1:06:41 PM | Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 0 | 127 | 257 | 2,506
12/16/2009 1:07:00 PM | Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 2 | 247 | 491 | 4,754
12/16/2009 1:07:19 PM | Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 246 | 247 | 248 | 4,283
12/16/2009 1:07:38 PM | Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 124 | 288 | 495 | 4,612
12/16/2009 1:07:57 PM | Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 494 | 618 | 743 | 9,435
12/16/2009 1:08:16 PM | Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 603 | 613 | 618 | 8,638
12/16/2009 1:08:35 PM | Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 616 | 617 | 618 | 8,066
12/16/2009 1:08:54 PM | Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 521 | 587 | 620 | 7,153
12/16/2009 1:09:13 PM | Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 496 | 619 | 743 | 7,088
12/16/2009 1:09:32 PM | Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 493 | 555 | 739 | 5,955
12/16/2009 1:09:51 PM | Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 494 | 618 | 740 | 6,290
12/16/2009 1:10:10 PM | Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 496 | 589 | 620 | 5,666
12/16/2009 1:10:29 PM | Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 496 | 579 | 743 | 5,288
12/16/2009 1:10:48 PM | Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 494 | 618 | 743 | 5,386
12/16/2009 1:11:07 PM | Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 495 | 588 | 742 | 4,888
12/16/2009 1:11:26 PM | Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 493 | 556 | 619 | 4,411
12/16/2009 1:11:45 PM | Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 494 | 588 | 743 | 4,481
12/16/2009 1:12:04 PM | Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 496 | 578 | 743 | 4,227
12/16/2009 1:12:23 PM | Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 494 | 584 | 620 | 4,104
12/16/2009 1:12:42 PM | Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 372 | 557 | 744 | 3,766
12/16/2009 1:13:01 PM | Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 495 | 619 | 744 | 4,051
12/16/2009 1:13:20 PM | Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 0 | 121 | 364 | 657
12/16/2009 1:13:39 PM | Page Reads/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page reads/sec | 1 | 3,755 | 7,509 | 23,584

Back to the top

## SQLServer:Buffer Manager Page writes/sec

> Description: Number of physical database page writes issued. 80 – 90 per second is normal, anything above, check the lazy writer/sec and Checkpoint pages/sec counter, if these counters are relatively high then, this indicates a memory constraint.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:Buffer Manager\Page writes/sec | 0 | 8 | 547 | 19 | 26 | 2 | 1 | 1

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
12/16/2009 1:04:28 PM | Page Writes/sec > 90 | \\DB04\SQLServer:Buffer Manager\Page writes/sec | 0 | 137 | 547 | 25,893

Back to the top

# SQLServer:General Statistics

## SQLServer:General Statistics Logins/sec

> Description: Total number of logins started per second. Greater than 2 per second may indicate that applications are not correctly using connection pooling.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:General Statistics\Logins/sec | 0 | 0 | 2 | -3 | 0 | 0 | 0 | -

Back to the top

## SQLServer:General Statistics Logouts/sec

> Description: Total number of logouts started per second. Greater than 2 per second indicates that the application is not correctly using connection pooling.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:General Statistics\Logouts/sec | 0 | 0 | 2 | -2 | 0 | 0 | - | -

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\SQLServer:General Statistics\Logouts/sec | 0 | 0 | 2 | -2

Back to the top

## SQLServer:General Statistics User Connections

> Description: Number of users connected to the system. The number of users currently connected to the SQL Server.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:General Statistics\User Connections | 11 | 18 | 21 | 60 | 4 | 19 | 20 | 21

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
12/16/2009 1:04:28 PM | Possible disparity between User Connections and Batch Requests per second | \\DB04\SQLServer:General Statistics\User Connections | 11 | 12 | 12 | 47.3684210526316
12/16/2009 1:04:47 PM | Possible disparity between User Connections and Batch Requests per second | \\DB04\SQLServer:General Statistics\User Connections | 11 | 11 | 11 | -47.3684210526316
12/16/2009 1:05:44 PM | Possible disparity between User Connections and Batch Requests per second | \\DB04\SQLServer:General Statistics\User Connections | 11 | 11 | 11 | -18.9473684210526

Back to the top

# SQLServer:Latches

## SQLServer:Latches Latch Waits/sec

> Description: Number of latch requests that could not be granted immediately and had to wait before being granted. In other words, these are the amount of latches, in a one second period that had to wait.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:Latches\Latch Waits/sec | 0 | 67.105 | 2,010.048 | 7,025.623 | 204.403 | 27.997 | 6.96 | 1.695

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
12/16/2009 1:04:09 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.397 | 9.635 | 26.202 | 0
12/16/2009 1:04:28 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 25.538 | 60.73 | 110.79 | 9,681.208
12/16/2009 1:04:47 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 2.78 | 41.721 | 77.923 | 3,039.707
12/16/2009 1:06:03 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0 | 0.499 | 1.198 | -288.514
12/16/2009 1:06:41 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 7.181 | 206.715 | 348.054 | 4,667.668
12/16/2009 1:07:00 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 175.544 | 227.277 | 288.678 | 4,581.939
12/16/2009 1:07:19 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 175.184 | 229.149 | 307.888 | 4,159.201
12/16/2009 1:07:38 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 13.127 | 152.942 | 238.86 | 2,468.446
12/16/2009 1:07:57 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.396 | 1.741 | 3.19 | -124.642
12/16/2009 1:08:16 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0 | 0.943 | 2.385 | -126.682
12/16/2009 1:08:35 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.594 | 1.785 | 3.369 | -106.25
12/16/2009 1:08:54 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.597 | 1.736 | 3.173 | -99.785
12/16/2009 1:09:13 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.596 | 1.261 | 2.59 | -99.167
12/16/2009 1:09:32 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 1.188 | 1.686 | 2.575 | -88.597
12/16/2009 1:09:51 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.797 | 1.489 | 2.382 | -85.748
12/16/2009 1:10:10 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.199 | 1.194 | 2.188 | -84.178
12/16/2009 1:10:29 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.398 | 1.393 | 2.785 | -78.085
12/16/2009 1:10:48 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.992 | 1.736 | 2.583 | -71.27
12/16/2009 1:11:07 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 1.195 | 1.989 | 2.583 | -65.853
12/16/2009 1:11:26 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.596 | 1.239 | 2.572 | -69.169
12/16/2009 1:11:45 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.595 | 1.89 | 3.381 | -61.148
12/16/2009 1:12:04 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.994 | 1.658 | 2.587 | -60.456
12/16/2009 1:12:23 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.596 | 1.638 | 2.388 | -58.279
12/16/2009 1:12:42 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.597 | 1.839 | 3.585 | -54.709
12/16/2009 1:13:01 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.398 | 1.888 | 2.982 | -52.423
12/16/2009 1:13:20 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 0.398 | 0.797 | 1.595 | -57.743
12/16/2009 1:13:39 PM | Latch Wait Times are greater than 10 milliseconds on average | \\DB04\SQLServer:Latches\Latch Waits/sec | 234.003 | 1,122.025 | 2,010.048 | 7,025.623

Back to the top

## SQLServer:Latches\Total Latch Wait Time Total Latch Wait Time (ms)

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

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:Latches\Total Latch Wait Time (ms) | 0 | 380 | 12,325 | 42,612 | 1,232 | 141 | 24 | 17

Back to the top

# SQLServer:Memory Manager

## SQLServer:Memory Manager Memory Grants Pending

> Description: Current number of processes waiting for a workspace memory grant. Memory Grants Pending records the number of connections that are waiting for memory before they can begin processing a memory intensive query such as a sort or hash operation. Connections that wait in this state for a long enough time will eventually get an 8645 error (A time out occurred while waiting for memory resources to execute the query. Rerun the query). A spid waiting in this state will have a waittype of 0x0040 (RESOURCE_SEMAPHORE) in sysprocesses. If this counter remains above zero for any significant amount of time then you will need to track down what queries are doing sorts/hashes and run them through Index Tuning Wizard to see if they can get a more efficient plan.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:Memory Manager\Memory Grants Pending | 0 | - | 0 | 0 | 0 | - | - | -

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\SQLServer:Memory Manager\Memory Grants Pending | 0 | - | 0 | 0

Back to the top

## SQLServer:Memory Manager Total Server Memory (KB)

> Description: Total amount of dynamic memory the server is currently consuming

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:Memory Manager\Total Server Memory (KB) | 1,208,072 | 1,230,206 | 1,257,472 | -164,312 | 15,075 | 1,231,530 | 1,233,369 | 1,235,586

Back to the top

# SQLServer:SQL Statistics

## SQLServer:SQL Statistics Batch Requests/sec

> Description: Number of SQL batch requests received by server. This counter measures the number of batch requests that SQL Server receives per second, and generally follows in step to how busy your server's CPUs are. Generally speaking, over 1000 batch requests per second indicates a very busy SQL Server, and could mean that if you are not already experiencing a CPU bottleneck, that you may very well soon. Of course, this is a relative number, and the bigger your hardware, the more batch requests per second SQL Server can handle. From a network bottleneck approach, a typical 100Mbs network card is only able to handle about 3000 batch requests per second. If you have a server that is this busy, you may need to have two or more network cards, or go to a 1Gbs network card. Note: Sometimes low batch requests/sec can be misleading. If there were a SQL statements/sec counter, this would be a more accurate measure of the amount of SQL Server activity. For example, an application may call only a few stored procedures yet each stored procedure does lot of work. In that case, we will see a low number for batch requests/sec but each stored procedure (one batch) will execute many SQL statements that drive CPU and other resources. As a result, many counter thresholds based on the number of batch requests/sec will seem to identify issues because the batch requests on such a server are unusually low for the level of activity on the server. We cannot conclude that a SQL Server is not active simply by looking at only batch requests/sec. Rather, you have to do more investigation before deciding there is no load on the server. If the average number of batch requests/sec is below 5 and other counters (such as SQL Server processor utilization) confirm the absence of significant activity, then there is not enough of a load to make any recommendations or identify issues regarding scalability.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:SQL Statistics\Batch Requests/sec | 0 | 2 | 9 | 38 | 2 | 1 | 1 | 1

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
* | OK | \\DB04\SQLServer:SQL Statistics\Batch Requests/sec | 0 | 2 | 9 | 38

Back to the top

## SQLServer:SQL Statistics SQL Compilations/sec

> Description: Number of SQL compilations.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 4 | 18 | 66 | 3 | 4 | 4 | 4

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
12/16/2009 1:04:09 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 1 | 2 | 0
12/16/2009 1:04:28 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 2 | 4 | 5 | 505
12/16/2009 1:04:47 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 2 | 6 | 13 | 477
12/16/2009 1:05:06 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 0 | 1 | -38
12/16/2009 1:05:25 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 0 | 1 | -26
12/16/2009 1:05:44 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 1 | 5 | 17
12/16/2009 1:06:03 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 0 | 1 | -19
12/16/2009 1:06:22 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 0 | 1 | -18
12/16/2009 1:06:41 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 8 | 11 | 18 | 237
12/16/2009 1:07:00 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 4 | 8 | 14 | 138
12/16/2009 1:07:19 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 5 | 10 | 15 | 175
12/16/2009 1:07:38 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 3 | 7 | 11 | 97
12/16/2009 1:07:57 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 5 | 10 | 61
12/16/2009 1:08:16 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 3 | 6 | 27
12/16/2009 1:08:35 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 5 | 9 | 54
12/16/2009 1:08:54 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 5 | 10 | 49
12/16/2009 1:09:13 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 3 | 10 | 28
12/16/2009 1:09:32 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 5 | 10 | 43
12/16/2009 1:09:51 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 1 | 4 | 9 | 27
12/16/2009 1:10:10 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 4 | 10 | 33
12/16/2009 1:10:29 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 7 | 10 | 52
12/16/2009 1:10:48 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 3 | 9 | 16
12/16/2009 1:11:07 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 1 | 5 | 9 | 34
12/16/2009 1:11:26 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 5 | 11 | 33
12/16/2009 1:11:45 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 3 | 9 | 14
12/16/2009 1:12:04 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 1 | 6 | 9 | 41
12/16/2009 1:12:23 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 3 | 10 | 13
12/16/2009 1:12:42 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 0 | 5 | 11 | 28
12/16/2009 1:13:01 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 1 | 5 | 9 | 27
12/16/2009 1:13:20 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 1 | 4 | 9 | 18
12/16/2009 1:13:39 PM | A ratio of more than 1 SQL Compilation for every 100 Batch Requests per second | \\DB04\SQLServer:SQL Statistics\SQL Compilations/sec | 6 | 11 | 16 | 66

Back to the top

## SQLServer:SQL Statistics SQL Re-Compilations/sec

> Description: Number of SQL re-compiles. This needs to be 0 as much as possible. A recompile can cause deadlocks and compile locks that are not compatible with any locking type.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0

Back to the top

### Alerts

An alert is generated if any of the above thresholds were broken during one of the time intervals analyzed. An alert condition of OK means that the counter instance was analyzed, but did not break any thresholds. The background of each of the values represents the highest priority threshold that the value broke. A white background indicates that the value was not analyzed by any of the thresholds.

Time | Condition | Counter | Min | Avg | Max | Hourly Trend
--- | --- | --- | --- | --- | --- | ---
12/16/2009 1:04:28 PM | A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations | \\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec | 0 | 0 | 1 | 69
12/16/2009 1:08:16 PM | A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations | \\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec | 0 | 0 | 1 | 2
12/16/2009 1:08:35 PM | A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations | \\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec | 0 | 0 | 1 | 3
12/16/2009 1:09:51 PM | A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations | \\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec | 0 | 0 | 1 | 2
12/16/2009 1:10:48 PM | A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations | \\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec | 0 | 0 | 1 | 1
12/16/2009 1:11:07 PM | A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations | \\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec | 0 | 0 | 1 | 2
12/16/2009 1:11:45 PM | A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations | \\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec | 0 | 0 | 1 | 1
12/16/2009 1:12:04 PM | A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations | \\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec | 0 | 0 | 1 | 2
12/16/2009 1:13:01 PM | A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations | \\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec | 0 | 0 | 1 | 2
12/16/2009 1:13:20 PM | A ratio of more than 1 SQL Re-Compilation for every 10 SQL Compilations | \\DB04\SQLServer:SQL Statistics\SQL Re-Compilations/sec | 0 | 0 | 1 | 1

Back to the top

# SQLServer:Locks

## SQLServer:Locks Lock Requests/sec

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

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:Locks(_Total)\Lock Requests/sec | 0 | 1,648 | 23,448 | -7,571 | 4,251 | 591 | 545 | 523

Back to the top

## SQLServer:Locks Lock Waits/sec

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

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:Locks(_Total)\Lock Waits/sec | 0 | 0 | 2 | 6 | 0 | - | - | -

Back to the top

## SQLServer:Locks Lock Wait Time (ms)

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

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:Locks(_Total)\Lock Wait Time (ms) | 0 | 7,890 | 489,188 | 1,544,804 | 43,216 | - | - | -

Back to the top

## SQLServer:Locks Number of Deadlocks/sec

> Description: Number of lock requests that resulted in a deadlock.

Back to the top

### Counter Instance Statistics

Overall statistics of each of the counter instances. Min is the minimum value recorded in the entire log, Avg is the average value of the entire log, Max is the maximum value recorded in the entire log, and Trend is the net, average, difference between data points of the entire log.

Name | Min | Avg | Max | Hourly Trend | Std Deviation | 90th Percentile | 80th Percentile | 70th Percentile
--- | --- | --- | --- | --- | --- | --- | --- | ---
\\DB04\SQLServer:Locks(_Total)\Number of Deadlocks/sec | 0 | - | 0 | 0 | 0 | - | - | -

Back to the top
Disclaimer: This report was generated using the Performance Analysis of Logs (PAL) tool. The information provided in this report is provided "as is" and is intended for information purposes only. The authors and contributors of this tool take no responsibility for damages or losses incurred by use of this tool.