I guess I have to ask “the” question:
What do you hope to gain by virtualizing? Are you looking to consolidate SQL servers in order to reduce the number of physical servers?
If that’s the case, then a little leg work may be in order. You may want to do some performance trending on your current servers to determine average CPU and memory utilization.
If your databases require only marginal utilization of their current resources as you suspect, these physical servers may be prime candidates for virtualization, and therefore consolidation.
Hopefully this helps,
Hello, somthing to think of in all of this is that you will want to use Raw diskmappings on the raid arrays or you will get no benefit from your arrays, as Jeff stated find out what is the biggest resource drain at current?
Disk IO/ Mem/CPU or NIC, also things to consider isthat VMware does not use active active on connections to your san so on fibre you are going to get 4gb (at present).
one thing to think of would be using DRS and affinity rules to keep certain SQL Vms away from each other and try to keep Memroy hungry servers with CPU intensive servers to split an equal load over physical machines. if you have ESX 3.5 use the consolidation tool to assess the SQL boxes however this does not measure NIC or disk IO unfortunatly however it is a start.
I have seen lots of succesful SQL production VM’s which have worked well, specifically write and read specific servers together.
Even the VirtualCenter instance can be virtulaised succesfully as HA does not use it and will bring it back up in the event of a failure.
hope this helps