SQL Server 2012 AlwaysOn Availability Group Setup
How to Establish a Performance Baseline for a SQL Server Instance
In this blog post, I discuss how to use a free utility called DVDStore to establish a performance metric for a SQL Server instance. It establishes this number based on the raw performance of the instance, which benchmarks the overall impact of the CPU, memory, storage, and instance-level configurations. Check it out here!
Your DBAs need direct access to VMware vCenter. At a minimum, they need read-only access to the performance statistics for their virtual machines hosting their database server, as well as the host that they reside upon. I consider a requirement for all DBAs to have vCenter performance statistics access in environments where I have any sort of say in the matter, and here’s why.
In the early days of virtualization, the core focus of virtualization was primarily consolidation. You could achieve quite high consolidation ratios, with some even as great as 20 to 1. This consolidation worked great for applications like file and print servers, development workloads, or other very lightly used servers. The virtualized servers that hold these servers are technically overcommitted on resources, but the workloads are so low that the end users would not notice the effects.
However, as more and more business-critical workloads are virtualized, maintaining this same level of consolidation is guaranteed to rear its ugly head in the form of performance degradation of the virtual machines. Most VMware administrators realize that resource overcommitment is slowing down their most intensive servers.
How can this be, you ask?
Few administrators know about a simple metric called CPU Ready.