Page History

...

You can adjust the scheduled refresh rate for a monitored virtual SQL Server SQL Server instance by right-clicking the instance name , and then selecting Properties.

Differences in statistics

You may notice some difference differences in your statistics, such as SQL Diagnostic Manager displaying a higher OS CPU usage OS CPU usage than your VM CPU usageVM CPU usage. While the hypervisor manages resources efficiently, it is possible that the demand for physical resources is greater than what is available. For example, a guest OS on a virtual machine submits a batch of work to a CPU. However, all of the physical CPUs are committed to other work, so there is no physical CPU available on the host to process the work. In this situation, the VM waits for a CPU to become available to process its work. While it is waiting, the guest OS is unaware of the wait and assumes that it is simply taking longer for the CPU to process this batch of work, and the OS thinks it is using more CPU power than it is actually using.

Remember that SQL Diagnostic Manager uses the additional overhead of the hypervisor to calculate the VM metrics. In this situation, the hypervisor knows the VM is just waiting for a CPU, so it does not charge the VM for CPU processing power while it is waiting. The result is that the guest OS reports that it is using the additional processing power, however, the hypervisor simply reports what is actually used. In this situation, your CPU usage CPU usage metrics that are reported by Windows are higher than what is reported by VMware or Hyper-V for that VM.

Available metrics related to your VMs

A monitored virtual SQL Server SQL Server instance appears in the Servers pane in the same way as a monitored physical SQL Server SQL Server instances. Click the appropriate virtual instance, and SQL Diagnostic Manager displays the same dashboard panels as for a monitored physical SQL Server SQL Server instance, but also include includes specific metrics for the VM and host server.

...