SQL 2005 VM on ESXi 4 will not use more CPU resources from host.

We have SQL 2005 running on Windows Server 2003 as a VM on an ESXi 4 host.  The host started off with single socket 4 core CPU.  Due to high CPU utilization, we added a second socket 4 core CPU.  The VM is running by itself on the host.  What is happening is, when you look at the CPU usage in windows its stilll high averaging 80%-90%.  If you look at the performance tab of the VM in ESXi its also reporting 80% plus.  However if you look at the performance tab of the host itself without any other VMs assigned, it only reports about 35% usage.  The VM is set to 4 vCPU and the host itself has 2 socket of 4 core totaling 8.  Any ideas?
autocribAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
whats the issue?

poor SQL performance, slow queries?

was performance poor with 1 vCPU?

adding many vCPU can have a detrimental effect?

if you have single VM only, why not just install on Bare Metal, with hypervisor?
0
coolsport00Commented:
The issue could be memory, not CPU; Since you're using 2K3, & if you're using 32bit, you only have a 4GB limit. That could be the problem... (but, also depending upon license Edition - Ent, DC, etc)

~coolsport00
0
autocribAuthor Commented:
Of course when it peaks at 100% we have sql requet timeouts, the server was converted with the existing 4 cpu so we left it at 4 vCPU.  This has been running fine at this setting for years.  We of course have grown and added load to the SQL server.  Is it a good idea to set it back to only one vCPU at this point? We converted to a virtual enviroment to take advantage of seamless hardware upgrades and management so no way we are going back to bare metal.
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

autocribAuthor Commented:
No we can rule out RAM or disk usage ever since we upgraded to 32GB and 64bit editions of both 2003 and sql 2005, disk usage have dropped to barely anything and we have ample RAM available.  The only thing that have steadily climb over the years have been CPU usage.  I believe this is more of a ESXi issue then windows or SQL.  Any ESXi experts out there?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Yes move the SQL database off the ESXi server, and it will solve your issue.
0
coolsport00Commented:
It could be the host. Sometimes DBs don't play nice with vSphere. Same goes with Terminal Services. Can they run on vSphere? Sure. Is it supported. Absolutely. But, is it the best for resource? No, not necessarily...
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
We have been working with clients and moving, via Virtual to Physical conversions at moving SQL servers from virtual to physical servers, because the Hypervisor sucks to much resources from the SQL server on bare metal.

So if the performance of your database as a virtual machine does not meet your requirements I would suggest the same course of action.

As an example we used a HP DL360 G5, Dual Processor Quad Core 3.0GHz, 32GB RAM, single virtual machine with 8GB RAM, 2 vCPU.

Querys took 13 minutes to respond, flatlined the VM at 100%, and also the Host.

Same configuration without the hypervisor, queries were instant, no CPU issues.

It was permamently migrated back to a physical VM. Adding additional resources, cpu, memory, did notbhelp.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Video of the Performance we experienced on troublesome SQL VM

Video - Poor Microsoft SQL Performance caused by Virtualisation - Not all servers are equal!
0
autocribAuthor Commented:
Upgrading to ESXi 5 enabled the option for the VM to user 8vcpu.  It now allows for the single VM to fully utilize both socket and all 8 cores.  Usage on the host went from 100% down to 60% usage.  Thanks for you input but it was a ESXi issue and we are running fine with MS SQL 2005 now.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
autocribAuthor Commented:
The issue was with ESXi 4 and the particular hardware compatibility.  The experts comments was on the course of getting away from virtualization which was not an option for us.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.