Experts Exchange connects you with the people and services you need so you can get back to work.
Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.
People get in trouble trying to virtualize SQL Server by not treating it as a SQL Server and planning things like Disk IO for SQL. If you think you can present a single LUN from a SAN to a host, format it for VMFS and then carve up 16 servers worth of VMDK's off that LUN and have one or more of those be for SQL Server and you are going to have good performance, your up for severe disappointment. You still need to have dedicated disk arrays from the SAN for database files, log files, and tempdb, and they need to be presented to the host as separate LUNS, and ideally, they will be RDMs and not VMFS volumes, this eliminates the hypervisor from the storage utlization and provides faster IO with lower CPU usage. The same prinicpals for RAID configuration that you'd apply to a physical server still apply to a virtual machines underlying disk IO subsystem.
Open in new window
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Please enter a first name
Please enter a last name
Must be at least 4 characters long.
Join and Comment
From novice to tech pro — start learning today.
Premium members can enroll in this course at no extra cost.