为什么核心受限的SQL Server VM的成本与未受限的相同? [英] Why do core constrained SQL server VMs cost same as unconstrained?

问题描述

这似乎确实是定价错误.受核心限制的VM的目的是为了节省软件许可费用.直接从Azure网站开始.针对SQL Server或Oracle收取的许可费将仅限于活动vCPU 计数，而包括操作系统许可在内的计算成本与基于底层vCPU"的原始大小保持不变.

This really seems like a pricing mistake.  The point of the core constrained VMs is to save money on software licensing.  Straight from the Azure website.. "The licensing charged for SQL Server or Oracle will be constrained to the active vCPU count while the compute cost, which includes OS licensing, remains the same one as the original size based on "underlying vCPU".

不过，美国东部2带有SQL Ent的GS4-8的价格与完全爆炸的GS4带有SQL Ent的价格($ 10.88/hr)完全相同.我希望它会减少25％左右，因为我应该只为SQL的8个内核而不是16个内核支付费用.这种奇怪的定价遍布所有人 受限制的系列，这似乎使它们毫无意义.我们只能在BYOL方案中节省许可费用吗?这是没有道理的，但是如果是这样，应该将其调出.

Yet the price of a East US 2 GS4-8 w/SQL Ent is the exact same as a full blown GS4 w/SQL Ent ($10.88/hr).  I would expect it be about 25% less as I should only be paying to license 8 cores of SQL instead of 16.  This strange pricing is across all the constrained series, which seems to make them entirely pointless.  Are we only able to save the licensing money in a BYOL scenario?  This would not make sense, but if it is the case, it should be called out.

我很早以前就已经打开了一张支持票，但是除了这就是价格"以外，没有其他答案.感谢您的帮助.

I already opened a support ticket on this quite awhile ago, but was unable to get an answer other than "this is the price". Thanks for any help.

托尼

推荐答案

The vCPU count can be constrained to one half or one quarter of the original VM size. These new VM sizes have a suffix that specifies the number of active vCPUs to make them easier for you to identify.

例如，当前的VM大小Standard_GS5带有32个vCPU，448 GB RAM，64个磁盘(最大256 TB)和80,000个IOP或2 GB/s的I/O带宽.新的VM大小Standard_GS5-16 和Standard_GS5-8分别具有16个和8个活动vCPU，同时保留了Standard_GS5的其余规范，用于内存，存储和I/O带宽.

For example, the current VM size Standard_GS5 comes with 32 vCPUs, 448 GB RAM, 64 disks (up to 256 TB), and 80,000 IOPs or 2 GB/s of I/O bandwidth. The new VM sizes Standard_GS5-16 and Standard_GS5-8 comes with 16 and 8 active vCPUs respectively, while maintaining the rest of the specs of the Standard_GS5 for memory, storage, and I/O bandwidth.

针对SQL Server或Oracle收取的许可费用仅限于新的vCPU计数，其他产品应根据新的vCPU计数计费.这导致 VM规格与活动(可计费)vCPU的比率增加了50％到75％.这些新的VM大小仅在Azure中可用，从而允许工作负载以(每核)许可成本的一小部分推动更高的CPU利用率.此时，计算 包括操作系统许可在内的成本与原始大小保持不变.

The licensing fees charged for SQL Server or Oracle are constrained to the new vCPU count, and other products should be charged based on the new vCPU count. This results in a 50% to 75% increase in the ratio of the VM specs to active (billable) vCPUs. These new VM sizes that are only available in Azure, allowing workloads to push higher CPU utilization at a fraction of the (per-core) licensing cost. At this time, the compute cost, which includes OS licensing, remains the same one as the original size.

有关详细信息，请参见Azure VM大小以了解更多 具有成本效益的数据库工作负载和"受限制的支持vCPU的VM大小 a>".

For more information, see Azure VM sizes for more cost-effective database workloads and "Constrained vCPU capable VM sizes".

您可以共享支持请求的SR号吗?

Could you share the support request SR number?

这篇关于为什么核心受限的SQL Server VM的成本与未受限的相同?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！