Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
maxpanic
Starting Member
2 Posts |
 Posted - 2011-03-30 : 16:38:37
|
| We have implemneted virtualization in our production environments for Sql Server 2008 R2, Sql Server 2008, Sql Server 2005, etc. We are on hyper-V and core server. I really don't like it at all. Here is why.Our server has four hex core processors. when you virtualize those processors you effectively end up with 24 cores. Sql Server standard edition costs about 1/5 the price of enterprise edition. We won't pay for enterprise edition regardless and won't use it. Standard edition is limited to 4 cpus, through virtualization this limits the resources available to the sql server to 4 cores.If your on the raw hardware with sql server 2008 R2 standard then you can use all 4 cpus, thus 24 cores all available in sql server standard. Once you virtualize the limits of sql server standard through virtualization become only 4 cores as the virtualization abstracts the cpus into cores that appear to be cpus. This one factor is the reason I regret moving to virtualization. Perhaps I am wrong, if so please tell me how to deal with this problem.Thanks,Max |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2011-03-30 : 17:52:11
|
| VMWare. |
 |
|
|
maxpanic
Starting Member
2 Posts |
Posted - 2011-03-31 : 14:12:13
|
| We have actually tested this out with VMWare ESXi server and the same thing occurrs. Bottom line, if you want more than 4 cores on your database server and you don't want to spend the extra money going above standard edition of Sql Server stay away from virtualization. |
|
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2011-04-03 : 23:54:49
|
| This is silly. You're limited to 4 with or without virtualization. How many schedulers does your non-virtualized SE instances see? The answer is 4, no? |
|
|
|
|
|
|
I don't like virtualization in production