Microsoft per core and per core with CAL rules count rights from physical cores on a host, or from virtual cores on each virtual machine. In Software Asset Management you match each rule to its metric, link Software Assurance as a separate entitlement, and set cluster and Hyper-V counts so hosts are sized correctly.
Which Microsoft license models SAM covers
Three models cover the server rules on this page. Each maps to a metric chosen on the entitlement, and the metric decides what is counted.
| Model | Typical products | What gets counted | Metric in SAM |
|---|---|---|---|
| Per Core | SQL Server, BizTalk Server | Physical cores on a host, or virtual cores on a VM | Per Core |
| Per Core (with CAL) | Windows Server, System Center | Cores plus user or device access licenses | Per Core (with CAL) and a User or Device CAL metric |
| Software Assurance (SA) | Upgrade and mobility rights on a perpetual license | Active rights on a separate SA entitlement | SA entitlement linked to a base entitlement |
Two decisions shape the count in each case: whether you license the physical host or each virtual machine, and whether the host sits in a cluster. Cloud installations follow separate rules, so this page covers on-premise deployments.
Per core rules for SQL Server
Physical-core licensing counts the cores on the server, where physical cores equal the CPU count multiplied by the cores in each CPU. The Enterprise edition can be licensed this way, with a minimum of four licenses per physical processor. A two-processor host therefore starts at eight licenses, even if it has fewer cores.
SQL Server Standard cannot be licensed by physical cores. It is licensed through the virtual machines it runs in, with a minimum of four licenses per VM. The count equals the virtual cores on that machine: CPU count multiplied by cores per CPU and by threads per core.
| Rule | Physical host (Enterprise) | Virtual machine (Standard and Enterprise) |
|---|---|---|
| Licenses required | Physical cores | Virtual cores |
| Minimum | 4 per physical processor | 4 per VM |
| Software Assurance or subscription | Needed to run unlimited VMs | Required |
| Virtual machine rights | Without SA, VMs equal to the core licenses on the server. With SA and a fully licensed host, unlimited VMs | Licenses can be reassigned within a server farm as often as needed. The 90-day rule applies when moving to another farm or cloud provider |
Software Assurance also adds failover rights. A licensed environment can run passive replicas ahead of a failover: one high availability replica and one disaster recovery replica in separate environments, plus one disaster recovery replica in a single VM or instance on Azure.
The components of one SQL Server license cannot be split. Any operating system environment running a licensed component needs its own license, so a server running any licensed SQL Server component is counted in full.
Per core with CAL rules for Windows Server
On a physical server, Windows Server licenses equal the physical cores, with a minimum of eight per physical processor and sixteen per server. Device or user CALs are also required for each user or device that reaches the server, and they are recorded under their own metric.
Virtualization rights depend on the edition. Standard edition, with every host core licensed and license stacking applied, covers two virtual machines. Two more need the host to be licensed again. Datacenter covers unlimited virtual machines once all cores on the host are licensed. License mobility is not available for Windows Server, but a license can be reassigned to servers as often as every 90 days.
Inside a VM, the count moves to the virtual layer. It equals the virtual cores on the machine, with a minimum of eight licenses per VM, and it requires active Software Assurance or a subscription.
Clusters and Hyper-V change the host license count
Virtualization clusters on VMware vSphere, Microsoft Hyper-V and Nutanix AHV raise a question single servers do not. If a virtual machine running a Microsoft product can migrate to another host, the receiving host must be licensed as though that machine already runs on it. Live migration and host affinity both affect how far a machine can move, so the cluster configuration sets the count.
For SQL Server, licensing the physical host for a cluster can only use Enterprise edition licenses, and it counts the VMs that could run on the host. That can cost more, so compare it with individual VM licensing before choosing it. For the wider cost picture, see licensing and cost factors to plan for.
Windows Server clusters are sized differently. Density equals the active operating systems divided by two, so a host with eight active operating systems has a density of four. Standard edition covers two operating system environments per license set, with a minimum of 16 rights per physical server. Datacenter covers an unlimited number of environments.
The optimization compares density against the ratio of Datacenter cost to non-Datacenter cost, held in the system property com.snc.samp.windowserver.license.threshold. Its default is 4.59. Low-density hosts receive Standard rights from smallest to largest, and high-density hosts receive Datacenter rights from the highest density down. A cluster that runs out of suitable rights is marked unlicensed.
For Hyper-V, discovery finds the hypervisors, the virtual machines and the Microsoft server products inside them. For how discovery data is prepared, see software discovery and normalization in SAM Professional. When Windows Server is licensed at the physical layer, the Licenses required field in the License Metrics Results of the Microsoft publisher overview populates for the parent server that represents the physical host. For Windows Server Standard, the cost-based optimization licenses the physical hosts first and then the VMs, combining both layers.
When Software Assurance changes the count
SA is recorded as its own entitlement. On the Standard form, set License type to SA and enter the rights the agreement grants in Active rights, which is required. SA entitlements cannot take user or device allocations. For the general model, see software entitlement explained.
The link to the base license is made in the Related Entitlements list. Each link records the active rights passed across, the software entitlement, the related entitlement and a domain that defaults to global. Linking can split a perpetual entitlement. Suppose a perpetual entitlement holds 50 active rights and only 20 are tied to SA. The 20 stay linked on the original record, and the other 30 become a separate perpetual entitlement with no SA attached.
Validation runs against the active rights of all linked entitlements. If the SA rights do not cover the perpetual rights, an error message appears. The Upgraded Entitlements list appears only for the Step-up license type, which is the route for linking a newer version under a maintenance contract.
Importing an MLS
Microsoft issues a Microsoft License Statement (MLS) as an Excel file, and you must request it from Microsoft before importing. Start from Create entitlement, choose the option to import from an Excel file, set Import type to Microsoft license statement, and select the file. Turning on automatic creation of contracts builds parent and child contracts linked to the entitlements that import successfully.
The import record shows rows processed, rows successful, rows with errors, and SA or Step-up entitlements still in the build state. Errors are reviewed from the Review import errors view, set to Needs review, corrected and re-imported. Unlinked SA or Step-up entitlements are then related to a base entitlement.
Reading the optimization outputs
The Microsoft Core License Optimization Reports table records each recommended change. Its fields show the product, whether the target is a cluster or standalone host, the virtualization technology, whether host affinity is configured, and the rights each layer needs. Current License Consumption and its layer show what is in use today, Recommended License Consumption shows the target, and Conservative License Consumption shows the count without any optimization. Host affinity applies to clusters only, so it is set to false on a standalone host.
The Microsoft Server Infrastructure and License Consumption report covers cloud, on-premise and standalone environments, with exemptions and their reasons. A scheduled job refreshes it weekly, and it sits under License usage in the Software Asset Workspace. Savings appear in the Optimization and savings dashboard, split into potential savings and realized savings.
The cost-based optimization supports per core for SQL Server and BizTalk Server, and per core with CAL for Windows Server, Core Infrastructure Server and System Center.
For the compliance side, read the publisher license reconciliation overview and the guide to reading software reconciliation results. The counting basis on this page feeds those results. The software license optimization guides show where these rules fit in a full program.
Frequently asked questions
Can SQL Server Standard be licensed by physical cores?
No. Standard is licensed through the virtual machines it runs in, with a minimum of four licenses per VM.
Why does a clustered Windows Server host need more licenses than the VMs running on it today?
A virtual machine that can migrate to a host is counted there, as though it already runs on that host. Live migration and host affinity determine how far a machine can move.
Does licensing by virtual machine need Software Assurance?
Yes. Licensing by individual VM requires active Software Assurance or a subscription for both SQL Server and Windows Server.
What happens to a perpetual entitlement when only some of its rights are linked to SA?
It splits. The linked rights stay on the original record with the SA association, and the rest become a second perpetual entitlement.
Which setting controls the Standard and Datacenter split for Windows Server clusters?
The system property com.snc.samp.windowserver.license.threshold, which defaults to 4.59 and reflects the ratio of Datacenter cost to non-Datacenter cost.
Can an MLS be imported without first getting it from Microsoft?
No. The MLS is an Excel file that Microsoft provides on request, and the import flags rows with errors and SA or Step-up entitlements that still need a base entitlement.