Microsoft Per Core licensing rules

  • Release version: Xanadu
  • Updated August 1, 2024
  • 5 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Microsoft Per Core licensing rules

    The Microsoft Per Core licensing model is widely used for server products like SQL Server and BizTalk Server, especially when tracking users or devices is complex, such as with internet-facing software. This model applies differently for on-premise and cloud installations, with cloud usage typically following Bring Your Own License (BYOL) policies. On-premise licensing can be done either by physical cores on the server or by individual virtual machines (VMs), but not by clusters. The Software Asset Management (SAM) application can help allocate licenses manually or optimize allocation for cost-effectiveness.

    Show full answer Show less

    Licensing by Physical Cores

    This method, introduced in 2016, applies primarily to SQL Server Enterprise Edition and is not available for SQL Server Standard Edition.

    • License count: Number of physical cores on the server (calculated as CPU count × core count).
    • Minimum licenses: 4 licenses per physical processor.
    • Virtualization rights: Without Software Assurance or subscription, the number of VMs equals the number of core licenses; with active Software Assurance, unlimited VMs can run on a fully licensed server.
    • Failover rights: Permits one passive failover replica for high availability and disaster recovery scenarios per licensed server environment with active Software Assurance.
    • Component licensing: All components within SQL Server require their own license per operating system environment (OSE); components cannot be separated under a single license.
    • Cluster virtualization: Licensing must cover all physical hosts on which VMs can migrate, such as in VMware vSphere or Microsoft Hyper-V clusters, due to live migration capabilities.

    Note: Only SQL Server Enterprise Edition supports this method, and it can be more costly since physical hosts must be licensed based on potential VM migration.

    Licensing by Virtual Machines

    Introduced in 2022, this licensing option applies to both SQL Server Standard and Enterprise Editions and requires Software Assurance or subscription licenses.

    • License count: Number of virtual cores on a VM (calculated as CPU count × core count × CPU thread count).
    • Minimum licenses: 4 licenses per virtual machine.
    • License mobility: Licenses can be reassigned within the same server farm without restriction; moving licenses outside the farm or to another cloud provider is subject to a 90-day rule.
    • Failover rights: Similar to physical core licensing, allows passive failover replicas for high availability and disaster recovery with active Software Assurance or subscription licenses.
    • Component licensing: Each operating system environment running SQL Server components requires its own license; components cannot be split across licenses.

    Practical Implications for ServiceNow Customers

    • Choose licensing by physical cores if using SQL Server Enterprise Edition and managing physical hosts, keeping in mind the licensing cost and requirements for all hosts in a virtualization cluster.
    • Use licensing by virtual machines for both SQL Server Standard and Enterprise Editions, especially when Software Assurance or subscription licensing is in place, to gain flexibility and license mobility.
    • Leverage the Software Asset Management application to optimize license allocation and ensure compliance with Microsoft rules, reducing unnecessary licensing costs.
    • Understand failover and virtualization rights to properly license high availability and disaster recovery configurations.
    • Be aware that SQL Server components must be licensed per OSE, and licenses cannot be fragmented across components or VMs.

    The Per Core licensing model is used by many Microsoft server products, such as SQL Server and BizTalk Server. It's useful when counting users or devices connecting to the software is difficult, often for internet-facing software.

    Therefore, the Per Core licensing model is commonly used for enterprise software like Microsoft SQL Server.

    The licensing rules for on-premise installations of these products and the cloud installations are separate. The cloud licensing rules follow Bring Your Own License (BYOL). For more information, see Licensing rules for BYOL and BYOS.

    To license the on-premise installation of these products using the Per Core licensing model, consider the following two options.
    • Licensing by physical cores, also known as licensing by physical hosts
    • Licensing by individual virtual machines
    Note:
    You can either allocate to individual hosts or individual virtual machines, not to cluster.

    You can either allocate manually, or the Software Asset Management application can automatically select the most cost-effective licensing option based on optimization criteria. The number of core licenses required depends on whether you’re licensing the physical server based on its physical cores or licensing individual virtual machines.

    For more information about how to perform allocation, see Allocation management and how the Software Asset Management application performs automated optimization, see View realized and potential cost-based licensing optimizations for Microsoft.
    Note:
    Both options, whether licensing by physical cores or licensing by individual virtual machines, come with their own set of Microsoft rules that must be followed. For more information, see SQL Server.
    Other licensing models, such as the Server CAL licensing model, are also available for these products.

    Licensing by physical cores

    The Software Asset Management application supports licensing by physical core rules, introduced by Microsoft in 2016.
    Table 1. Licensing by physical core rules
    Rule SQL Server Standard SQL Server Enterprise
    Applicability Not allowed
    Note:
    Only allowed to be licensed through individual virtual machines.
    		 The number of licenses required equals the number of physical cores on the licensed server.

    The physical cores on servers are equal to CPU count * Core count.
    Min licenses required Not allowed
    Note:
    Only allowed to be licensed through individual virtual machines.
    		 4 licenses per physical processor
    Virtualization rights Not allowed
    Note:
    Only allowed to be licensed through individual virtual machines.
    • Without software assurance or subscription licenses, run virtual machines equal to the number of core licenses assigned to the physical server.
      Note:
      Each additional virtual machine would require an additional core license.
    • With active software assurance or subscription license, run an unlimited number of virtual machines if all physical cores on the server are fully licensed.
    Failover rights Not allowed
    Note:
    Only allowed to be licensed through individual virtual machines.
    		 For each server operating system environment (OSE) licensed with SQL Server subscription licenses covered by active Software Assurance, you can use the following passive replicas ahead of a failover event:
    • One passive failover replica for High Availability in a separate OSE
    • One passive failover replica for Disaster Recovery in a separate OSE
    • One passive failover replica for Disaster Recovery in a single virtual machine or instance on Azure
    Components services licensing Not allowed
    Note:
    Only allowed to be licensed through individual virtual machines.
    		 The software components of a single SQL Server license can't be separated. An OSE running any of the licensed components of SQL Server requires its own license. For more information about SQL Server components, see Editions and supported features of SQL Server 2022.
    When deploying Microsoft products like Windows Server or System Center (using the Per Core license model) on cluster virtualization technologies such as VMware vSphere, Microsoft Hyper-V, or Nutanix Acropolis HyperVisor (AHV), the number of licenses required for the physical host depends on the virtual machines that could potentially migrate to it within the cluster.

    Technologies like VMware vMotion, which enables live migration of virtual machines across all hosts, and host affinity, which helps lock virtual machines to hosts within a cluster, manage the movement of virtual machines across hosts. To understand more about cluster virtualization technology and its support on the Software Asset Management application, see Understanding your cluster infrastructure.

    According to Microsoft licensing rules, if a virtual machine with a Microsoft product like Windows Server installed is hosted on one server but can potentially migrate to another, the destination server must be licensed as if the virtual machine is already running on it.

    Tip:
    As only the Enterprise edition license can be used for this option and you must license the physical host based on the number of virtual machines that can run on it, this licensing option can be more costly.

    Licensing by virtual machines

    The Software Asset Management application supports licensing by individual virtual machines rules, introduced by Microsoft in 2022.

    Note:
    This licensing option is the only option available for SQL Server Standard Edition when using the Per Core licensing model.
    Table 2. Licensing by individual virtual machines rules
    Rule SQL Server Standard and SQL Server Enterprise
    Required number of licenses Equals the number of virtual cores on the virtual machine

    The virtual cores on servers are equal to CPU count * Core count * CPU thread count.
    Min licenses required 4 licenses per virtual machine
    Software assurance or subscription license
    Note:
    The option to license by virtual machine is only available with software assurance or a subscription license.
    		 Required
    License mobility within Server farms (Software assurance benefit)
    Note:
    Licenses can be reassigned within the same server farm as often as needed. The 90-day rule applies only when moving to another server farm or cloud provider.
    		 Supported
    Component services licensing The software components of a single SQL Server license can't be separated. An OSE running any of the licensed components of SQL Server requires its own license. For more information about SQL Server components, see Editions and supported features of SQL Server 2022.
    Failover rights For each server OSE licensed with SQL Server subscription licenses or licenses covered by active software assurance, use the following passive replicas ahead of a failover event:
    • One passive failover replica for High Availability in a separate OSE
    • One passive failover replica for Disaster Recovery in a separate OSE
    • One passive failover replica for Disaster Recovery in a single virtual machine or instance on Azure