利用SQL Server向下到核心...

我以前提到过这个，但许可问题不要激动我，因为他们让你进入法律言论，这可能会在帽子下降时变化。当出现漏洞时，您可以确定供应商的律师将快速关闭它。我对产品在技术上工作的更感兴趣。但我经常询问Microsoft SQL Server“每个处理器”许可以及它如何技术方式与产品相关联。让我们来看看。Microsoft决定了遍历套接字而不是核心的多核处理器。这使我们在定价中得到了一个大休息，并将微软与甲骨文区分开来，这显然每核心收取50％的许可费。使用SQL Server，四核处理器需要一个处理器许可证，但SQL Server将使用所有四个核心，仿佛是单个处理器。成本低，性能高。什么可能更好？ A question came up in a recent class: “I have a server with 4 x quad-core processors running SQL Server Standard Edition with 4 processor licenses. Does this mean SQL Server is using all 16 cores?”. On the technical side, SQL Server sees each core as a separate processor. SQL Server technically cannot tell the difference between a core in a Multi-Core processor and a "Single-core" processor, if that’s what we call them now. The cores are treated the same regardless. To SQL Server they are all processors. Check this out in SSMS under the Server Properties, Processors page. You’ll see each core listed as a processor. In our example, 16 processors are listed. However, SQL Server technically limits the "max degree of parallelism" by Edition. For instance, the Standard Edition is limited to 4 which means the number of processors employed to run a single statement, for each parallel plan execution is limited to 4 processors. See: http://msdn.microsoft.com/en-us/library/ms181007(v=SQL.105).aspx So each statement can use a maximum of 4 processors in parallel but SQL Server will choose any 4 processors that are available to it. Therefore multiple statements running at the same time may run against a separate set of 4 processors. So SQL Server Standard Edition will use all 16 cores but only 4 at a time. So the answer to our question is Yes and No. If you wanted to have each statement use all 16 processors at the same time you would need the Enterprise Edition which allows up to 32 processors to be used by a single statement. But soon I am sure we will have a multi-core processor that has more than 32-cores. Intel has been testing an 80-core CPU. Will this force Microsoft to rethink their licensing? Hopefully not. We’ll see. Cheers Brian Licensing changes in SQL Server 2008 R2… //m.amiribrahem.com/community/node/61780