For example, if you have a two-processor server and want to run a total of four VOSEs, you can purchase two Standard edition licenses and assign them to the same server. Additional examples are shown in the following table. Windows Server R2. Windows Server R2 captures the experience Microsoft has gained from building and operating public clouds to deliver a highly dynamic, available, and cost-effective server platform for your datacenter and private cloud.
The following information provides an overview of your key licensing options. Licensing editions Compare features in all editions to determine the ideal solution for your virtualization and cloud computing needs. Datacenter edition is ideal for customers who want to have a highly virtualized private and hybrid cloud environment. As always, it provides access to all the product features and enables unlimited instances of Windows Server with each license, enabling your virtual environment to grow as you do.
The licensing for Datacenter edition will continue to be processor plus CAL Client Access License , with each license covering up to two physical processors on a single server. Standard edition is ideal for those customers who want to have a physical or lightly virtualized environment. This edition enables you to run up to two virtual instances of Windows Server with each license and provides all the same features as Datacenter edition.
Developer and Express editions continue to be distributed without changes in licensing or pricing. SQL Server provides a variety of virtualization and cloud benefits that help you save money on database licensing and retain flexibility in your database deployments. With SQL Server, you can:. Connect with a Microsoft solution provider. Contact your Microsoft account representative. Buy online at the Microsoft Store.
SQL Server product page. SQL Server licensing guide. Introduction to per core licensing and basic definitions. SQL Server Build intelligent, mission-critical applications using a scalable, hybrid database platform that has everything built in—from in-memory performance and advanced security to in-database analytics.
SQL Server site. The type of licensing you will purchase will be dependent on the edition of SQL Server which you purchase, which will be dependent on the features you expect from SQL Server. SQL Server comes in the following editions:. Each edition has limitations on the licensing models that can be used to purchase it. Please see my interpretation below, illustrating which licensing models can be used with which editions. The Express and Compact Editions are free, and do not require licenses.
Microsoft also provides a table with this information in the document entitled 'SQL Server Licensing Reference Guide', which is linked to at the end of this tip. Follow the arrows in the diagram below from your desired edition of SQL Server or from your current licensing model to find which editions or licensing models are suitable for you:. Each edition of SQL Server differs in features.
For example, Developer Edition has all the features of Enterprise Edition, but cannot be used in a commercial environment. Standard Edition does not include features such as table partitioning, online index rebuilds or backup compression.
Express Edition will handle databases up to 10GB in size only. Since the focus of this discussion is on licensing models rather than a blow-by-blow account of feature differences between editions, please see the More Links section for information on the different features of SQL Server and how they compare in order to make the best choice of edition for your organization's needs. The document 'What's New in SQL Server ' has a good summary of new features and their availability between versions, while those of you familiar with these restrictions in R2 and below will note that most restrictions still apply.
See below for Microsoft's one-page summary of the feature sets that come with Enterprise, Business Intelligence and Standard Editions note this is not a complete list :. For example, if your organization employs people, 20 of whom work in the Finance department which has two SQL Server installations on two separate servers, 2 server licenses and 20 CALs would be required. Starting with , Microsoft recognized the shift onto core-based computing, where two or more cores are used for parallelism and better efficiency on production IT systems.
Microsoft decided to capitalize on this and protect the licensing fees which would arguably suffer as focus shifted from increasing the number of processors to increasing the number of cores. The new core-based system means each core used in a SQL Server installation must be licensed separately with some exceptions, see below.
These licenses are sold in 'packs' of two and one pack of two is roughly equivalent in price to the older per-processor license. Thus, although more licenses are required and other factors such as price adjustment and inflation have affected the price , there may not be a significant difference to the overall price when relicensing for , depending on your circumstances.
Note that hyper threading is ignored for core licensing purposes when licensing physical servers. However - something called 'Core Factor' comes into play here. Core factor refers to the factor one must multiply by when determining the licenses required, depending on the type of processor one has. AMD processors are licensed differently from Intel ones. And non-Intel, non-AMD processors are licensed differently still. Here are the rules:. Note that when ordering the licenses, you must divide the number of licenses by two to determine how many 'packs' to order.
Don't order double the amount you need by accident! As you can see, this isn't an entirely fair model. A four-core Intel processor requires 16 licenses even though performance-wise it will be thoroughly outstripped by two processors with two cores each, due to increased parallelism.
For this reason, in a single-core architecture, you may wish to make sacrifices with e. Microsoft stipulate that for those customers installing SQL Server in virtual environments, a core license is required for every virtual core in the virtual environment that is supported by one hardware thread this means physical processor core OR hyperthread.
Be very wary when using hyperthreading on physical machines that support VMs, as licensing costs can double despite having no additional physical computing power!
This means that if there exists a VM with multiple virtual cores, one license is required for each virtual core even if supported by fewer hardware threads than cores. However, if multiple hardware threads are supporting fewer cores, one license is required for each hardware thread. Core factoring does not apply for VMs. There is a minimum four licenses required per VM regardless of VM cores. In example number 3 above, the VM is under provisioned against the physical machine so you may wish to add more VMs so that VM core licensing is appropriate to get better value for or even save money , or turn off hyperthreading, or go for maximum virtualization see below for more details to remove the need to license per core on each VM.
Note that physical licensing wins out over virtual licensing. Sign in to vote. The questions I'm are: 1. Is it legal to license in this way? Wednesday, June 27, AM. Hi, Thanks for your posting. Thank you for your understanding. TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.
Lawrence TechNet Community Support.
0コメント