Windows Server and SQL Server licensing, explained with real numbers.

Both products are licensed per physical core. The edition you choose, whether Software Assurance stays in place, and whether workloads run on premises, in Azure or in another cloud decide what a host costs.

Windows Server and SQL Server are both licensed per physical core, and the same host can cost very different amounts depending on how you license it. The edition, whether Software Assurance (SA) stays in place, and where the workload runs decide most of the bill.

The worked numbers below use Microsoft's current list prices. Read this guide alongside the Microsoft knowledge hub, the Microsoft SAM guide, the EA renewal guide, and our Vendor Shield subscription.

How does per core licensing work for Windows Server and SQL Server?

You license the physical cores in the host, whatever the workloads on it consume. Both products are sold in 2 core packs, Windows Server also in 16 core packs, and a set of minimums sets the floor on every server and VM.

Which core minimums apply?

• 16 cores per Windows Server host. Every physical host needs at least 16 core licenses, even when the hardware has fewer cores.
• 8 cores per processor for Windows Server. A two socket server with 6 cores per socket still needs 16 core licenses.
• 4 cores per processor for SQL Server. On a physical server you license every core, with at least 4 per processor. The 16 core host minimum does not apply to SQL Server.
• 4 cores per SQL Server virtual machine. A 2 vCPU VM licensed on its own still needs 4 core licenses, and licensing by VM is open only to licenses with active SA or subscription licenses.
• 8 cores per Windows Server virtual machine. Licensing Windows Server by individual VM needs active SA or subscription licenses and at least 8 core licenses per VM.

Core licenses are not the whole cost. Every user or device that accesses Windows Server also needs a Windows Server CAL. SQL Server Standard can instead be bought as Server plus CAL, at $989 per server and $230 per CAL, which is cheaper when a small, known group of users connects.

Should you buy Windows Server Standard or Datacenter?

Buy Standard for hosts that run a few VMs and Datacenter for densely virtualized hosts. A fully licensed Standard host covers 2 VMs and can be stacked for more; Datacenter covers unlimited VMs once every physical core is licensed.

Where does Datacenter start to cost less than stacked Standard?

At list price, Datacenter is cheaper from the 11th VM on a host. One Datacenter license costs about 5.8 times a Standard license at both 2022 and 2025 prices, so the crossover arrives with the sixth Standard stack.

On a 32 core host every figure doubles, and an equal discount on both editions leaves the crossover where it is. VM movement across a cluster does change it.

When does pay as you go through Azure Arc make sense?

Windows Server 2025 can also be billed through Azure Arc at $33.58 per core per month. A 16 core host then costs about $537 a month, or $6,447 a year, with no unlimited virtualization right. A year of that nearly buys a perpetual Datacenter license, so keep it for short lived or seasonal servers.

Which SQL Server edition do you need?

Most production databases fit Standard. Enterprise is for workloads that need its features, more cores per instance than Standard allows, or host level licensing with unlimited VMs.

• Express. Free. Limited to 10 GB per database in SQL Server 2022, 50 GB in SQL Server 2025, and 1 socket or 4 cores. It suits small applications, not production systems of any real size.
• Developer. Free for development and test, never for production workloads. SQL Server 2025 splits it into Standard Developer and Enterprise Developer to match the production edition.
• Standard. Mid range feature set, limited to the lesser of 4 sockets or 24 cores per instance in SQL Server 2022. SQL Server 2025 raises that to 32 cores and 256 GB of buffer pool memory.
• Enterprise. Full feature set with no core cap. Licensing every physical core with SA adds unlimited virtualization on that host.

What does SQL Server Enterprise cost on a real host?

Say you run a 32 core VMware host with six SQL Server Enterprise VMs of 8 vCPUs each. The table compares licensing each VM with licensing the host, at current list prices, with SA taken at 25 percent of the license price a year. Licensing by VM requires SA, so it is included in every per VM row.

With six VMs, host licensing saves $120,984 up front, and the gap grows with every VM added. With two VMs, per VM licensing costs half as much as the host, SA included. Run it host by host before any true up.

How do the virtualization rules change your license count?

Virtualization changes what you count: physical cores when you license the host, virtual cores when you license the VM. The cluster design usually matters more than any single VM.

Windows Server in a virtual cluster

Each full set of Standard core licenses covers two VMs on one host, up to the licensed core count. Stack a second set on the same host to cover four VMs. Datacenter covers unlimited VMs on the host once every physical core is licensed.

Clusters cause most of the trouble because VMs move. Microsoft's terms allow a license to be reassigned to another server only once every 90 days, and Windows Server licensed by physical core has no mobility right that lifts it. Where VMs float, each host needs licenses for the most Windows VMs it can run, which pushes clusters toward Datacenter.

SQL Server in virtual machines

Standard is licensed per VM on the vCPU count, with the 4 core minimum, and that option needs SA or subscription licenses. Without them, Standard licensed on the physical cores runs only in the physical operating system. Enterprise can be licensed per VM, or on every physical core of the host, which with SA covers any number of VMs.

SA also allows licensed VMs to move between hosts in the same server farm as often as needed, instead of once every 90 days.

The unlimited virtualization right exists only while SA is active. When SA lapses, a fully licensed Enterprise host covers only as many SQL Server VMs as it has core licenses, and per VM licensing is no longer available.

Why we push back on dropping SA across every SQL Server host

A common cost cutting tip is to let SA lapse on SQL Server Enterprise once the version is stable. We disagree for virtualized and clustered hosts. SA carries unlimited virtualization, free VM movement within the farm, passive failover rights, License Mobility and Azure Hybrid Benefit.

Take the six VM host above with a second 32 core host running its passive failover replicas. With SA, the replicas are covered. Without it, the second host needs its own $241,968 of licenses, four years of SA on the first host.

Model the SA premium against the licenses you would need without it; it is usually cheaper. Drop SA only on physical, single instance servers that will not move to Azure.

How does Azure Hybrid Benefit reduce Windows Server and SQL Server costs in Azure?

Azure Hybrid Benefit applies on premises licenses covered by SA or subscription to Azure VMs and databases, so you pay only the base compute rate. It was earlier called the Azure Hybrid Use Benefit (HUB). It cuts Azure compute cost by up to 40 percent on Windows and up to 55 percent on SQL Server.

Five rules that decide what you get

1. SA or subscription is mandatory. The benefit applies only during the SA or subscription term. When it ends you renew, switch the VM to pay as you go, or remove the workload.
2. Per core mapping. On Windows, one core license covers one Azure vCPU, with at least 8 per VM. On SQL Server, one Standard core covers one vCPU, and one Enterprise core covers up to four vCPUs of SQL Server Standard on an Azure VM, or four vCores in the General Purpose tier.
3. A 180 day dual use period. During migration, licenses can run on premises and in Azure at the same time for up to 180 days.
4. Datacenter carries wider rights. Datacenter licenses can run on premises and in Azure VMs at the same time with no end date; Standard licenses must sit in one place after the 180 days. Datacenter on all cores of an Azure Dedicated Host covers unlimited Windows VMs there.
5. Azure Arc extends the benefit on premises. Servers you keep and connect through Azure Arc get Windows Server Management enabled by Azure Arc at no extra charge once you attest to SA coverage.

Pair the benefit with reservations

The benefit removes the license part of the VM price; reserved instances or a savings plan discount the compute part. Together they typically take compute 60 to 70 percent below pay as you go. Microsoft advertises up to 80 percent for Windows and 85 percent for SQL Server, which assumes the best region and term.

See our guides to Azure Hybrid Benefit and reservations against savings plans.

Can you move SQL Server licenses to AWS or Google Cloud?

Yes, through License Mobility through Software Assurance, provided SA is active. AWS, Google Cloud and Alibaba Cloud are Microsoft Authorized Mobility Partners. Azure uses Azure Hybrid Benefit instead.

Three conditions for License Mobility

• Active SA. The license must carry SA for as long as it runs in the provider's cloud.
• An authorized provider. The destination must be on Microsoft's Authorized Mobility Partner list.
• A verification form within 10 days. You file Microsoft's License Verification Form within 10 days of deploying the workload.

Windows Server is not eligible. On AWS or Google Cloud shared instances the Windows license is part of the provider's hourly rate, so price it before assuming you can bring your own. Our note on Microsoft licensing in cloud migration covers dedicated hosts.

Where can you cut Windows Server and SQL Server costs?

Five changes produce most of the savings, each on its own line of the bill. Three more protect them: pooling licenses across business units to cut shelfware, using the EA renewal to renegotiate SQL Server terms, and bringing in an independent audit defense adviser before the next Microsoft audit letter.

The ranges do not add together, because consolidation shrinks the core count that right sizing then applies to.

Windows Server and SQL Server license cleanly when the edition fits the workload, SA covers the virtualization rights you rely on, and Azure Hybrid Benefit follows the migration plan.

What will the Microsoft account team say, and how should you answer?

These are the lines we hear most often on server licensing, with our reply to each.

• "Move every host to Datacenter and the counting problem goes away." Ask for the host by host VM count first. Datacenter pays off from about 11 VMs per host or on clusters where VMs float.
• "SQL Server now runs across the cluster, so every host needs Enterprise." Ask which hosts actually run it. Pin SQL VMs to a named host group with affinity rules and license only those hosts.
• "Azure Hybrid Benefit means you must keep SA on everything." SA is needed only on the licenses that rely on it: those used in Azure, for unlimited virtualization or per VM licensing, for passive failover, or under License Mobility.
• "Switch SQL Server to subscription for flexibility." Compare over your holding period. An Enterprise 2 core pack costs $5,434 a year on subscription against $15,123 once plus about $3,781 a year of SA, so subscription stays cheaper for roughly nine years. Against a perpetual license without SA, it costs more after about three years, though that license loses per VM licensing and the other SA rights.

How do you check what you are actually running?

Build the count from your own systems before an audit or renewal, so Microsoft's figures are checked against yours.

• Physical cores. The host summary in vCenter or Hyper-V Manager shows sockets and cores; on a Windows host, Get-CimInstance Win32_Processor returns NumberOfCores per socket.
• SQL Server edition. Run SELECT SERVERPROPERTY('Edition'), SERVERPROPERTY('ProductVersion') on every instance, including test and departmental ones.
• Cores SQL Server sees. The sys.dm_os_sys_info view shows socket_count, cores_per_socket and cpu_count.
• Azure Hybrid Benefit status. Each Azure VM's configuration shows whether the benefit is on; centrally managed SQL Server benefit is assigned in Cost Management.
• Entitlements. Volume licensing records in the Microsoft 365 admin center list licenses, SA coverage and agreement dates.

Compare what is installed, what the hosts can run, and what you own. Our server licensing calculator handles the host arithmetic.

How does Redress help with Microsoft server licensing?

We run Microsoft server licensing work inside the Vendor Shield subscription, the Renewal Program, the Benchmark Program, and the Software Spend Assessment. Every engagement is led by a former Microsoft commercial executive who now works only for the customer.

See also our benchmarking service, read about us, find our locations, or contact the team.

What to do next

1. Inventory every host. Map each physical host to its cores and the VMs it runs or can run.
2. Score the edition mix. Standard against Datacenter for Windows, Standard against Enterprise for SQL Server.
3. Model Azure Hybrid Benefit. Compare the Azure compute saving with the SA premium that makes it possible.
4. Confirm SA coverage. Keep SA where unlimited virtualization, License Mobility or the benefit depends on it.
5. Right size the cores. Consolidate workloads onto fewer, denser hosts.
6. Consolidate licenses. Pool licenses across business units to reduce shelfware.
7. Plan the EA renewal. Start 12 months out and use it to renegotiate SQL Server terms and price holds.
8. Engage an audit defense partner. Have an independent adviser in place before Microsoft's next contact.

Frequently asked questions