Hello,
http://www.vmware.com/files/pdf/sql_server_virt_bp.pdf
Page 7 :
However, VMware recommends using the VMware enterprise-class hypervisor — ESX or the free ESXi — to deploy any virtualized SQL Server instances, even for development and test environments. When you use the hosted products, depending on configurations and guest operating system support, the disk I/O caching performed by the host operating system can provide unpredictable performance and application availability in corner cases.
This behavior is not likely to be found on the VMware hosted products.
I disagree.
Maybe in version 3.5, but with vSphere we have had excellent performance for SQL in our VMware environment. In fact we just finished converting a physical SQL server that was using direct storage (Dell MD3K) to a vSphere cluster running on an EMC CX3-40 and they've seen 5x-6x increase in performance.
I'm not saying that it might be slightly faster to use physical hosts direct attaching via 4GB FC to the EMC SAN, but given the additional HA capabilities, and the virtualization of the hardware (not being tied to maintenance contracts, and hardware refreshes) more than makes up for the "loss" of performance of not having it direct attached to dedicated physical hardware.
Mahendra,
The article you listed describes using vmplayer, which is a type 2 hypervisor (VM's hosted on a workstation platform). Anytime I hear someone mention SQL being a weakness in VMware, it's usually from someone loading VM workstation on some 1992 gateway (no offense gateway) laptop and trying to run SQL to see how it will run in production. I just want to vomit when I hear about scenarios like this. Any tier 1 application should always be tested on a type 1 hypervisor like a vSphere host. The article even mentions that you will "likely" not run into this problem on ESX. To me, this statement just leaves the door open to paranoia for those who do not understand a well constructed infrastructure for a tier 1 application.
SQL is not a weakness in ESX 4.x, or even 3.x. Built correctly, it will purr like a kitten. I have plenty of purr'in kittens in my environment.
-- James
Regarding Burdweiser's post... I 100% agree with your post and am grateful someone is willing to come on here and challenge the masses.
SQL will run fine, I have many a VMs doing it right now. It is key to remember to size your virtual environment the same as your physical environment, by this I mean, if you are going to give your physical box 5 spindles don't give your VM 4 spindles and then share it with 5 other VMs and expect to get the same performance. Also important to keep in mind is the number of CPUs and how a vCPU (core) relates to a physical CPU (socket with multiple cores).
Agreed James
SQL on VMware is not an issue. If you know what your doing, you know what your doing! PERIOD!
I've run and built 4 SQL 2005 Servers under VMware vCenter 4.0 U1 without an issue.
I've even built a VM for vCenter 4.0 U1 running a local instance of SQL. (DR Purposes with HeartBeat).
Im not even going to get started with Exchange!
Actions
More Like This
- Retrieving data ...








