Windows Server and Microsoft SQL Server are core infrastructure platforms — and two of the most complex products to licence correctly. This practical guide breaks down the main licensing models, covers virtualisation and client access scenarios, and provides tips to avoid common pitfalls for IT managers and procurement leaders alike.
Windows Server is licensed based on edition and number of processor cores in the physical server. Since Windows Server 2016, Microsoft uses a core-based licensing model. The two primary editions are Standard and Datacenter, both of which require Client Access Licences (CALs) for user or device access.
You must purchase licences for all physical cores on each server. Core licences are sold in 2-core packs. Microsoft requires at least 16 cores per server (even if the machine has fewer) and at least 8 cores per physical processor. Even a small single-socket 4-core server needs 16 core licences.
| Edition | VM Rights | When to Use | Stacking |
|---|---|---|---|
| Standard | Up to 2 Windows Server VMs on the licensed server (plus one physical host instance for Hyper-V) | Smaller environments with limited virtualisation needs, or where workload density is low | Additional core licences in 16-core increments — each set grants rights for 2 more VMs |
| Datacenter | Unlimited Windows Server VMs on the licensed server | High-density virtualisation, cloud workloads, environments with 4+ VMs per host | Not required — once all cores are licensed, run any number of VMs |
Each user or device accessing the server needs a CAL — either User CALs (licence a person to access any Windows Server) or Device CALs (licence a device used by any number of users). Exceptions: no CALs needed for internet-only external users (use External Connector instead), or for pure virtualisation hosts not providing services. Remote Desktop Services (RDS) requires additional RDS CALs.
If you run a server with 2 CPUs x 10 cores (20 total), Standard covers 2 VMs. For 6 VMs, you must licence 20 cores three times. At that point, Datacenter — licensing 20 cores once for unlimited VMs — is typically more cost-effective. The crossover point is usually around 3-4 VMs per host.
| Pitfall | What Goes Wrong | How to Avoid It |
|---|---|---|
| Under-licensing cores | Forgetting the 16-core minimum or the requirement to cover all physical cores. Common when ordering licences without checking physical CPU counts | Always double-check physical CPU counts and core counts when ordering licences. Verify the 16-core minimum and 8-core-per-processor minimum are met |
| Stacking Standard beyond its limits | Standard can quickly become more expensive than Datacenter if you need many VMs on a single host | If you need to stack Standard more than twice (>4 VMs on one host), calculate whether Datacenter would save money. Do the maths before committing |
| Ignoring CAL requirements | Purchasing server licences without accounting for CALs leaves you out of compliance. Every internal user or device accessing server services legally requires a CAL | Budget for CALs in addition to server licences. Track user and device counts. Include CALs in every server deployment budget |
| Using the wrong CAL type | Employees using multiple devices (PC, laptop, phone) are over-licensed with Device CALs. Shared-device environments (shift workers, kiosks) are over-licensed with User CALs | If employees use multiple devices, User CALs are usually more cost-effective. If many users share a few devices, Device CALs are better. Review periodically |
Windows Server virtualisation rights are among the most complex areas of Microsoft licensing. Our dedicated guide covers VMware, Hyper-V, and multi-cloud scenarios in detail.
Read the Virtualisation Guide →Microsoft SQL Server offers two primary licensing models: Server + CAL and Per Core. The best choice depends on your usage scenarios (number of users vs. processor power) and SQL Server edition.
| Edition | Licensing Models Available | Key Characteristics |
|---|---|---|
| Standard | Server+CAL or Per Core | Some feature and performance limitations but sufficient for many departmental or mid-tier applications. Flexible licensing options |
| Enterprise | Per Core only | Top-tier, full feature set, optimised for large-scale mission-critical deployments. Since SQL Server 2012, Enterprise has been licensed per core only — you cannot use the Server+CAL model |
One SQL Server licence per server/VM/instance, plus a CAL for each user or device accessing any SQL Server. Cost-effective for a small, defined user population. Not practical for external/public users (CALs for each would be impractical). SQL CALs are separate from Windows CALs — you need both.
Licence all CPU cores of the system/VM where SQL Server runs (sold in 2-core packs). No separate CALs needed — any number of users can access. Minimum of 4 core licences per instance. Advantageous for large/unpredictable user counts or external-facing databases. The only option for Enterprise edition.
With Software Assurance, you are typically allowed one passive failover instance at no extra licence cost, as long as it is truly passive (not serving clients except during failover). Without SA, any secondary server running SQL must be fully licensed. A major incentive for SA on large SQL deployments.
Even a small 2-vCPU VM requires 4 core licences minimum per SQL Server instance. If you dynamically change a VM’s vCPU count, update your licensing count accordingly. This is one of the most common audit findings.
| Pitfall | What Goes Wrong | How to Avoid It |
|---|---|---|
| Under-counting cores in virtual deployments | The 4-core minimum per VM is critical. If you allocate 2 vCPUs to a SQL VM and licence only 2 cores, you are not compliant — you still need 4 licences for that VM | Always licence a minimum of 4 cores per SQL Server instance regardless of actual vCPU count. Track vCPU changes and update licence allocations |
| Misusing Developer Edition in production | SQL Developer Edition is free with all Enterprise features, but strictly for non-production use only. Organisations occasionally use it in production to save costs — a compliance violation | Ensure all production instances use Standard or Enterprise. Audit all SQL installations to confirm edition and licence type match the use case |
| CAL overload | Using Server+CAL without tracking user/device counts leads to compliance issues as the organisation grows. There is no annual “CAL true-up notice” — it is on you to ensure coverage | Regularly review Active Directory or application user lists vs. purchased CALs. Budget for growth. Consider switching to Per Core if the CAL count becomes unmanageable |
| Mixing editions/features without proper licences | Having a Standard licence but implementing an Enterprise-only feature (like online indexing or certain BI features) is a compliance problem | Licence based on the edition of software bits installed/used. If you need Enterprise features, licence Enterprise. Audit feature usage regularly |
| Feature | Server + CAL | Per Core |
|---|---|---|
| Available For | Standard only | Standard & Enterprise |
| Licence Based On | Server instance + named users/devices | CPU cores of server/VM |
| User Access | Each user/device needs a CAL | Unlimited users — no CALs required |
| Best For | Small, defined user population (<25–30) | Large/unknown user counts, external users |
| Minimum | 1 server licence + CALs | 4 core licences per instance |
| External Users | Impractical — CAL per user | Ideal — no per-user tracking |
| HA (with SA) | 1 passive failover free | 1 passive failover free |
Single physical server with 8 cores, running Windows Server 2022 Standard as Hyper-V host with 2 VMs: one for Active Directory/file sharing, one for a small SQL Server Standard database used by 15 employees.
Windows Server: Licence 16 cores (8 actual + minimum = 16) with Standard edition — covers host + 2 VMs. Purchase 15 User CALs for all employees accessing domain and file server.
SQL Server: 15 users and one database VM — opt for SQL Standard Server+CAL model. Buy 1 SQL Standard server licence + 15 SQL CALs. Cost-efficient for small environment.
VMware cluster with 3 hosts (each 16 cores). Approximately 10 Windows Server VMs, 2 SQL Server instances (one customer-facing with hundreds of web users, one internal with 200 employees).
Windows Server: Each host may run 6–8 VMs — stacking Standard becomes unwieldy. Licence each host with Datacenter edition (16 cores per host) — unlimited VMs, no counting needed. Acquire 200 User CALs for employees across all Windows Servers.
SQL Server: Customer-facing DB (external users cannot be CAL’d) — SQL Enterprise Per Core mandatory. Internal DB (200 users) — Per Core more practical than 200+ CALs. Licence one host with 16 SQL Enterprise cores + SA for unlimited virtualisation rights. Internal Standard DB: 4 vCPUs = 4 SQL Standard core licences + SA for Licence Mobility.
After deploying Windows and SQL Server licences, continuously monitor usage. For Windows Server, ensure new VMs do not exceed your licensed counts (with Datacenter, this is not an issue). Track CAL usage — if your company hires more people, you will need more CALs. If you switch from individual use to shared devices (or vice versa), consider changing CAL types at true-up or renewal.
For SQL Server, monitor performance and load. If you see one instance heavily used, confirm you have assigned enough core licences for any vCPU increases. Watch for Enterprise features accidentally enabled on Standard servers. Conduct periodic internal audits — perhaps annually or before a Microsoft true-up — to verify licence entitlements match deployments.
Engage experts when architecting new environments or if your setup is not cost-optimal. An independent specialist might discover that your 200 SQL CALs cost more than switching to core licensing, or that a lightly used SQL Server could move to a more cost-effective edition. They also help stay compliant when Microsoft announces changes. Our Microsoft Optimisation Services cover exactly these scenarios — most engagements identify savings worth multiples of the advisory investment.
Assess your environment’s size and needs: How many cores? How many users? How many VMs now and in the future? Then choose the editions and licensing models that fit those parameters, balancing upfront cost with long-term flexibility. Always remember the CAL component — it is part of the total cost of ownership.
See how we have helped global enterprises save millions by optimising Windows Server, SQL Server, and EA licensing.
View Microsoft Cases →Microsoft requires a minimum of 16 core licences per physical server and at least 8 cores per physical processor. Even if the server has fewer physical cores, you must purchase the minimum. Core licences are sold in 2-core packs, so the minimum purchase is 8 packs (16 cores) per server.
The crossover point is typically around 3–4 VMs per physical host. Standard covers 2 VMs per set of core licences. If you need more VMs, you must “stack” Standard in 16-core increments. Once you exceed 4–6 VMs per host, Datacenter — which provides unlimited VM rights once all physical cores are licensed — is almost always cheaper. Run a cost comparison based on your specific core count and VM density.
Yes. Windows Server CALs and SQL Server CALs are completely separate products. A user accessing a Windows Server needs a Windows CAL. If the same user also accesses SQL Server (using the Server+CAL model), they also need a SQL CAL. These cannot be combined or substituted for one another.
When licensing SQL Server per core, Microsoft requires a minimum of 4 core licences per physical server or virtual machine instance. Even if the VM has only 2 vCPUs allocated, you must purchase at least 4 core licences. This is one of the most common audit findings — organisations frequently under-licence small SQL VMs.
No. SQL Server Developer Edition includes all Enterprise features but is licensed strictly for non-production use — development and testing only. Using Developer Edition in any production capacity is a licence violation that will be flagged in a Microsoft audit. Ensure all production instances run properly licensed Standard or Enterprise editions.
With active Software Assurance, you can run one passive failover instance of SQL Server at no additional licence cost, provided it is truly passive — not serving client requests except during an actual failover event. Without SA, every SQL Server instance, including standbys, must be fully licensed. For large SQL deployments, this HA benefit alone can justify the SA investment.
It depends on your access patterns. User CALs are typically more cost-effective when employees access servers from multiple devices (PC, laptop, phone, tablet). Device CALs are better when multiple people share a limited number of devices (shift workers, kiosks, shared terminals). Review your patterns periodically — you can switch CAL types at your next Enterprise Agreement true-up or renewal.
This is a compliance problem. Microsoft licences based on the edition of software bits installed and features used. If you enable an Enterprise-only feature (such as online indexing, advanced compression, or certain BI capabilities) on a Standard-licensed instance, you are technically using Enterprise and must hold Enterprise licences. Audit feature usage regularly to avoid this common mistake.
We provide independent Microsoft licensing advisory covering compliance assessments, licence optimisation, EA renewal negotiation, true-up preparation, and audit defence. Most engagements identify savings worth multiples of the advisory investment — whether that is switching from Standard stacking to Datacenter, moving from CALs to per-core licensing, or right-sizing SQL editions. Our Microsoft Optimisation Services are fully vendor-independent and fixed-fee.
Whether you need licence optimisation, compliance assessment, true-up preparation, EA renewal negotiation, or audit defence — our Microsoft licensing specialists deliver measurable savings and protect your interests. 100% vendor-independent.