Itâ€™s not often that youâ€™ll see me write a lengthy book review. Most book reviews are fluff telling you to buy or not to buy a book, but donâ€™t contain a lot of the â€œwhyâ€ or â€œwhy notâ€ to do so. But, every once in a while a book comes along that just strikes in all the right ways, especially if its topic is in a core focus of yours. The book â€œVirtualizing SQL Server with VMware: Doing IT Rightâ€ by VMware Press and authored by Michael Corey, Jeff Szastak, and Michael WebsterÂ (three of the brightest folks that I personally know), is a book that I feel every VMware administrator (and any other vendorâ€™s hypervisor administrator as well) should purchase and read twice, and Iâ€™ll tell you why in this review.
First and foremost, virtualizing business critical applications, in this case Microsoft SQL Server, is a challenge. The process is nowhere as easy as migrating a file server or preproduction sandbox. Processes and practices that may work well for some applications can cause serious heartburn, performance problems, and worse â€“ instability â€“ when virtualizing SQL Servers. VM administrators need to be aware of the differences, and this book delivers this knowledge and experience in droves.
This book is targeted at VMware administrators and not directly to SQL Server DBAs. Many technical references are made to infrastructure components that most DBAs have had no exposure to (and arguably should not have to worry about unless they are a nerd like me). However, DBAs should still read the book to get a small taste of what it takes to architect and manage the virtualized environment underneath their data. The knowledge of these layers is guaranteed to make them better DBAs, and will help both organizational silos speak the same language during architecture and triage situations.
The authorâ€™s collective experience in managing these systems is quite apparent as you progress through the book. Many how-toâ€™s and gotchyaâ€™s are described in detail. All are scenarios that I encounter frequently during my normal day in consulting around this topic. The advice presented is well thought out and shows the depth of the authorsâ€™ experience in the field.
The best part of the book is that the authors spend a great deal of time educating VMware administrators on what SQL Server is and how it uses the infrastructure underneath it as it stores and retrieves data to fulfill its requests. The authorsâ€™ style is very casual and informative, and makes each concept and topic very easy to understand and digest. For example, DBAs understand SQL Server high availability and disaster recovery. So do VM administrators. But, the two strategies are usually very different, and one group does not know the capabilities of the other technologies and how they contrast or complement each other. When you put them together, what works for one might not work for the other, and the arguments generally ensue. The authors educate the VMware administrator on how SQL Server handles high availability and disaster recovery, and suggests VMware-based processes and practices that complement and improve what SQL Server handles well, all while leveraging the right technology for each layer of the stack.
I feel that the real â€œmeatâ€ of the book comes in two sections â€“ chapters five to nine and ten to eleven. The first group describes each layer of the virtualized infrastructure and breaks down architectural, performance, and configuration tips on why (and not just how) specific recommendations and architectural decisions are usually best for SQL Server on VMware.
The last two chapters do a fantastic job describing the end-to-end baselining and benchmarking process that are so frequently absent in most environments, both physical and virtual. This process helps eliminate the â€œitâ€™s slowâ€ mentality that comes from subjectivity, and replaces it with a series of objective processes for putting performance metrics to each of these layers. These metrics are key for both helping to identify the root layer of performance issues if they arise, and also eliminates the finger pointing that accompanies the â€œitâ€™s your fault until you can prove otherwiseâ€ attitudes that are found in any organization.
No tech book is without its flaws, and a handful of items caught my attention while reading and re-reading this book.
The authors make a claim that CPU and memory hot-add should be enabled. I personally feel that itâ€™s not quite as black-and-white as this. Hot-add of resources in a guest is a great feature, but hot-add also disabled virtual NUMA presentation to the VM. Correctly-sized virtual NUMA and SQL Server can improve performance, and hot-add of resources expressly disables virtual NUMA. Iâ€™ve implemented both, based on need, and I would like to see a broader discussion on the pros and cons of this setting.
Next comes the recommendation for one dedicated physical CPU core for each virtual CPU core. In my experience, itâ€™s a great place to start, but itâ€™s almost always too conservative and ends up â€œwastingâ€ CPU time that you pay for in the form of SQL Server core-based licensing. Iâ€™d like to see this conversation include a discussion of using CPU Ready and Co-Stop times as a more objective metric for CPU overcommitment.
The jump straight into the discussion around hyper-converged architectures, in this case Nutanix, felt abrupt. Preceding this chapter should have been a short chapter comparing and contrasting the differences between rack servers, blade servers, and hyper-converged architectures. A solid discussion of how SQL Server is architected differently on each of these platforms, and the implications on performance, availability, and scalability would be a welcomed segue into the discussion on the emerging field of hyper-converged environments.
As with any first edition book, a handful of technical inaccuracies and academic practices are present, but I feel that none detract from the true mission of the book â€“ to educate VMware administrators on virtualizing SQL Server. Items such as references for a SQL Server data file per vCPU core or data file placement sound good in theory but in practice can be tough to manage as an environment scales. I feel confident that the authors will correct the items that have been pointed out by myself and others in the next version of the book.
Some of the new features included in the recent launch of vSphere 6.0, well after the release of this book, changes some of the recommendations made in the book. I know that this release will contribute to some changes in the next version of the book as well.
To summarize, I recommend this book without hesitation to any VMware administrator who has, or needs to, virtualized business critical applications â€“ and not just SQL Server. I give it 4.5 out of 5 stars, and look forward to seeing more from these authors in the future!