July 27, 2017 at 8:36 pm
Hi,
In the company I work for, we have a slowness problem in the SQL Server 2014 database.
Today came a "dba" here to "solve" the problem, according to him the problem of slowness is due to the fact of using Hyper-V , And his solution would be to migrate to VSphere where we would have a 400% performance gain over Hyper-V or even a physical machine.
Is that correct, what did he say?
July 28, 2017 at 5:43 am
augustos - Thursday, July 27, 2017 8:35 PMHi,In the company I work for, we have a slowness problem in the SQL Server 2014 database.
Today came a "dba" here to "solve" the problem, according to him the problem of slowness is due to the fact of using Hyper-V , And his solution would be to migrate to VSphere where we would have a 400% performance gain over Hyper-V or even a physical machine.
Is that correct, what did he say?
Specs and configs please!
July 28, 2017 at 6:01 am
Eirikur Eiriksson - Friday, July 28, 2017 5:43 AMaugustos - Thursday, July 27, 2017 8:35 PMHi,In the company I work for, we have a slowness problem in the SQL Server 2014 database.
Today came a "dba" here to "solve" the problem, according to him the problem of slowness is due to the fact of using Hyper-V , And his solution would be to migrate to VSphere where we would have a 400% performance gain over Hyper-V or even a physical machine.
Is that correct, what did he say?Specs and configs please!
2 x Intel Xeon E5-3630 v2
192GB RAM
4TB Raid5 SSD
SQL Server 2014 SP2
July 28, 2017 at 7:10 am
augustos - Friday, July 28, 2017 6:01 AMEirikur Eiriksson - Friday, July 28, 2017 5:43 AMaugustos - Thursday, July 27, 2017 8:35 PMHi,In the company I work for, we have a slowness problem in the SQL Server 2014 database.
Today came a "dba" here to "solve" the problem, according to him the problem of slowness is due to the fact of using Hyper-V , And his solution would be to migrate to VSphere where we would have a 400% performance gain over Hyper-V or even a physical machine.
Is that correct, what did he say?Specs and configs please!
2 x Intel Xeon E5-3630 v2
192GB RAM
4TB Raid5 SSD
SQL Server 2014 SP2
And the SQL Server configuration?
July 28, 2017 at 7:55 am
Tell us when the "slowness" occurs and what is it relative to. For example, have you recently migrated this instance to Hyper-V and then the problem occurred, or has it been on Hyper-V for some time and only recently started giving you performance issues?
Also, run the following to determine top wait states for this server and post back results.
https://www.sqlskills.com/blogs/paul/wait-statistics-or-please-tell-me-where-it-hurts/
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
July 28, 2017 at 7:58 am
I don't have a compare case Hyper-V versus VMWare
You might want to check the setup of the Hyper-V host , the Hyper-VM , cpu, network, attached storage
MS realises a 95% (of the barebone metal) performance in Hyper-V
Mentions a generation v2 machine, high performance power-profile, network jumbo frames, numa-considerations, no overcommitment and eventually SR-IOV (physical access network from guest) ; I would wait to implement SR-IOV, passthroughdisks, dynamic memory
Might be outdated (2013) hyper-v 2012 checklist
July 28, 2017 at 8:17 am
augustos - Thursday, July 27, 2017 8:35 PMHi,In the company I work for, we have a slowness problem in the SQL Server 2014 database.
Today came a "dba" here to "solve" the problem, according to him the problem of slowness is due to the fact of using Hyper-V , And his solution would be to migrate to VSphere where we would have a 400% performance gain over Hyper-V or even a physical machine.
Is that correct, what did he say?
This is ABSOLUTE RUBBISH, and the person that said it is either uninformed, a moron, or a VMWare salesperson (or some combination of those). Given comparable, modern editions, and PROPER CONFIGURATION(!!!), both VMWare and HyperV are capable of running massive-scale SQL Server environments with VERY little overhead.
I note that you cannot POSSIBLY have a "massive scale" need due to the low-end server configuration you are using.
I also question your use of the 36xx CPU variant. Can you specify why you went with that model for a SQL Server workload?
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy