SQL Server licensing is one of the most complex and expensive areas of Microsoft licensing: multiple models (per-core, Server+CAL, cloud PaaS, Azure Hybrid Benefit), edition choices, virtualisation rules, non-production rights, and cloud BYOL mechanics that all interact to determine your total cost. This master guide covers every licensing model with cost comparisons, non-production environment rights, cloud licensing across Azure and AWS, optimisation strategies, common pitfalls, and actionable recommendations for SAM professionals and CIOs.
This guide is part of our Microsoft licensing series. For edition selection, see SQL Server Edition Strategy. For virtualisation licensing, see Licence Mobility in Virtualised Environments. For compliance risks, see Common SQL Server Compliance Pitfalls.
| Model | How It Works | Best For | Key Considerations |
|---|---|---|---|
| Per-Core (On-Prem) | Licences per physical core (2-core packs, 4-core minimum). No CALs required. Unlimited users. | Large-scale, internet-facing, data warehouses, high/unpredictable user counts. | Higher base cost but simpler management. Enterprise per-core significantly more than Standard. |
| Server + CAL (On-Prem) | One server licence per instance plus separate CALs per user or device. Standard Edition only. | Small organisations or internal applications with limited, known user base (<50 users). | Cost-effective at low user counts. As users grow, CAL costs can exceed per-core. Not available for Enterprise. |
| Cloud PaaS (Azure SQL/RDS) | Licence included in service pricing (per-vCore or per-DTU). Pay-as-you-go or reserved. | Variable workloads, dev/test, OpEx preference, rapid scaling. | Simplicity and agility. Apply Azure Hybrid Benefit to reduce costs if you own eligible SA licences. |
| Azure Hybrid Benefit (BYOL) | Apply existing on-prem SQL licences with active SA to Azure VMs or Azure SQL, paying only compute/storage. | Cloud migration, hybrid deployments, DR in Azure, already own licences with SA. | Saves 40-50% on Azure SQL costs. Must be manually enabled. Licences must have active SA. |
Non-production environments present major cost-saving opportunities when managed correctly.
Common non-production mistakes. Running paid editions on test servers. Using DR replicas for reporting (invalidates free passive status). Assuming passive rights exist without SA. Not documenting which instances are passive vs active during audits.
Azure SQL Database and Managed Instance (PaaS). These fully managed services include the SQL Server licence in their pricing by default. You pay per vCore or per DTU with no separate licence required. If you own eligible SQL Server licences, applying Azure Hybrid Benefit reduces the Azure bill by approximately 30-50% by removing the licence component from the service cost.
SQL Server on Azure or AWS VMs (IaaS). Running SQL on cloud VMs is similar to on-premises licensing. Cloud providers offer licence-included VMs (SQL cost bundled in the hourly rate) and BYOL VMs (you supply your own licence). In Azure, enabling Hybrid Benefit converts to BYOL pricing. In AWS, Licence Mobility (an SA benefit) allows bringing licences to EC2 or Amazon RDS BYOL mode.
Avoiding double licensing. When migrating workloads to cloud, perform a licence reconciliation. If you shift a workload to Azure using licence-included pricing, re-harvest the on-prem licence. If using BYOL, ensure the on-prem instance is decommissioned. Monitor cloud SQL instances with tagging and reporting to ensure Hybrid Benefit is enabled where eligible.
| Pitfall | What Goes Wrong | How to Avoid It |
|---|---|---|
| Overprovisioning | Licensing all physical cores when SQL is capped to use fewer. Buying Enterprise "just in case." Shelfware and wasted budget. | Use monitoring tools to determine actual core usage. Licence for current needs with a buffer, not worst-case theoretical capacity. |
| Unlicensed passive nodes | Assuming DR/HA secondaries are free without SA. Running "passive" servers for reporting or backups. | Verify SA coverage for passive rights. If any secondary handles production activity, licence it fully. |
| Cloud licensing misalignment | Paying licence-included cloud pricing while on-prem licences remain active (double payment). Not enabling Hybrid Benefit. | Reconcile licences during migration. Enable AHB explicitly. Re-harvest freed on-prem licences. |
| Virtualisation licensing drift | VM clones creating unlicensed SQL instances. VM migration moving SQL to unlicensed hosts. | Require licence approval for every new SQL VM. Use discovery tools. Restrict SQL VMs to licensed hosts. |
| Renewal rubber-stamping | Renewing the same EA counts without reviewing actual needs. Overbuying "safety stock" unused for 3 years. | Conduct internal optimisation review before every renewal. Start conservative. Use true-up for growth. |