- On-Premises SQL Server Licence Models Explained
- SQL Server Editions: Enterprise vs Standard vs Developer
- SQL Server Licensing in Virtualised Environments
- Azure SQL Deployment Options and Licensing
- Azure Hybrid Benefit: Maximising Your Existing Investments
- On-Premises vs Azure: The Total Cost Decision Framework
- Negotiating SQL Server in Your Microsoft EA
On-Premises SQL Server Licence Models Explained
SQL Server on-premises is available under two fundamentally different licence models, and selecting the correct model for each deployment is the first decision that determines your total cost. The choice is not always obvious — and Microsoft sales teams are not incentivised to guide you toward the more cost-effective option for your specific situation.
Core-Based Licensing
Core-based licensing charges per physical or virtual core on the server running SQL Server. All cores on the physical processor must be licensed (with a minimum of 4 cores per processor), and licences must cover all cores on servers running SQL Server regardless of how many cores the database workload actually uses. Core-based licensing is the only option for SQL Server Enterprise edition and is required for any internet-accessible SQL Server instance where the user population is unknown or unconstrained.
The advantage of core-based licensing is unlimited user access — once the server is licensed by core, any number of users or devices can connect without additional licence cost. For high-user-count deployments, this model becomes progressively more cost-effective as the user population grows. The limitation is that even lightly utilised servers must be fully licensed for all cores, which can be expensive for high-core-count servers running modest SQL workloads.
Server Plus CAL Licensing
Server plus Client Access Licence (CAL) licensing charges a base server licence fee plus a separate CAL for each user or device that accesses the SQL Server instance. This model is available only for SQL Server Standard edition. It is cost-effective for small to medium deployments with a known, bounded user population — typically fewer than 25–30 users, at which point the core-based model typically becomes more economical depending on server hardware configuration.
The CAL model requires rigorous licence tracking: every user or device that accesses SQL Server must hold a valid CAL, including automated processes, service accounts making database queries, and scheduled jobs. In our advisory engagements, organisations using the CAL model frequently discover they have underestimated their access count — particularly when application service accounts are counted as requiring individual CALs. A full access audit before committing to this model is essential.
The most common SQL Server licensing overpayment we encounter is large organisations running SQL Server Standard on high-core-count servers under CAL licensing, where the per-core cost of Enterprise would actually produce better economics — and better performance — than the CAL model at their user counts.
SQL Server Editions: Enterprise vs Standard vs Developer
The edition selection determines which licensing model is available and what capabilities the database can leverage. SQL Server Enterprise provides unlimited cores, unlimited RAM, and the full feature set — including Always On Availability Groups with up to 8 secondary replicas, columnstore indexes, in-memory OLTP, and advanced partitioning. SQL Server Standard supports up to 4 cores (or 24 cores with the Server+CAL model) and 128GB RAM per instance, with a subset of the full feature set.
For production workloads above moderate scale, SQL Server Enterprise is typically required for performance and resilience reasons regardless of licence model. The relevant commercial question is whether any Standard edition deployments in your estate have been allowed to grow beyond Standard's technical limits — operating in a non-compliant configuration that a Microsoft licence audit would identify. A SQL Server estate audit should verify edition compliance across all deployments, not just licence quantity compliance.
| Edition | Max Cores | Max RAM | Licence Model | Best For |
|---|---|---|---|---|
| Enterprise | Unlimited | Unlimited | Core only | Production, high availability, large scale |
| Standard | 4 cores/24 CAL | 128 GB | Core or CAL | Small/medium workloads, dev, departmental |
| Developer | Unlimited | Unlimited | Free (non-prod only) | Development and testing only |
| Express | 4 cores | 1.4 GB | Free | Small databases, embedded apps |
SQL Server Licensing in Virtualised Environments
Virtualised SQL Server environments introduce licensing complexity that is disproportionate to the technical effort of running SQL in a VM. The fundamental principle: unless you licence the entire physical host, SQL Server licences must be assigned to each virtual machine's allocated core count — you cannot licence "SQL Server on a VM" without either licensing all the physical cores that VM might run on, or using the Enterprise unlimited virtualisation right.
SQL Server Enterprise provides an unlimited virtualisation right: if you licence all physical cores on a server with SQL Server Enterprise Core licences and maintain active Software Assurance, all virtual machines on that host can run SQL Server Enterprise at no additional SQL licence cost. This is the "licence the host, not the VMs" approach, and it is the most cost-effective model for dense virtualised SQL Server environments — particularly where VM mobility (VMotion, live migration) is used, since each physical host the VM might run on must otherwise be licensed independently.
SQL Server Standard does not provide unlimited virtualisation. Each Standard VM must be individually licensed for the cores allocated to that VM (minimum 4 cores). For virtualised Standard deployments, the per-VM licensing model is manageable for small estates but becomes administratively complex at scale. The intersection of SQL Server Standard licensing and VMware environments has historically been one of the most contested areas in Microsoft licence audits — ensure your virtualisation licensing position is explicitly documented and defensible. For context on Oracle's similar virtualisation rules: Oracle Partitioning Rules: VMware, Hyper-V and Cloud.
Azure SQL Deployment Options and Licensing
Microsoft offers three primary Azure SQL deployment targets, each with different licensing implications and operational models.
Azure SQL Database (Fully Managed PaaS)
Azure SQL Database is a fully managed relational database service with a serverless or provisioned compute model. It offers near-full SQL Server compatibility without the management overhead of OS and instance administration. Licensing is included in the Azure compute cost — either as a full price (including SQL licence) or at a discounted rate with Azure Hybrid Benefit applied. Azure SQL Database is best suited for net-new cloud-native applications and for migration of on-premises databases that do not have complex SQL Server Agent jobs, linked server dependencies, or other instance-level features that are not supported in the PaaS model.
Azure SQL Managed Instance
Azure SQL Managed Instance provides near-100% SQL Server feature compatibility in a managed PaaS service. It supports the SQL Server Agent, cross-database queries, linked servers (with limitations), CLR, Database Mail, and most on-premises SQL Server features — making it the preferred migration target for complex on-premises SQL Server workloads. Pricing follows a vCore model, with Azure Hybrid Benefit available to reduce cost materially if you have existing SQL Server Enterprise licences with active SA.
SQL Server on Azure Virtual Machines
SQL Server on Azure VMs provides complete SQL Server feature compatibility and full OS-level control. It is required for workloads with SQL Server features not supported by Managed Instance, or for organisations that require custom OS configuration. Licensing can be pay-as-you-go (inclusive of SQL licence cost, at full Microsoft list price) or via Azure Hybrid Benefit (bringing your own SQL Server licence and paying only the Azure compute cost). SQL Server on Azure VMs also benefits from the 180-day concurrent use right during migration — running the same SQL Server workload on-premises and in Azure simultaneously for up to 180 days without additional licence cost.
Azure Hybrid Benefit: Maximising Your Existing Investments
Azure Hybrid Benefit (AHB) is the most material cost reduction mechanism available to organisations with existing SQL Server Enterprise licences and active Software Assurance. It allows those on-premises licences to be applied to Azure SQL workloads, replacing the full pay-as-you-go Azure rate (which includes an embedded SQL licence charge) with the base Azure compute cost alone.
The financial impact is substantial: for a SQL Server Enterprise workload running on a 16-vCore Azure SQL Managed Instance, the full pay-as-you-go rate might be approximately $5,000/month. With Azure Hybrid Benefit applied using existing Enterprise licences, the same instance could cost approximately $2,000–$2,200/month — a saving of over 55% versus list price. The exact saving depends on the instance tier and region, but Enterprise edition AHB consistently produces 50–70% cost reductions on compute costs.
The mechanics: each on-premises SQL Server Enterprise Core licence with active SA maps to 1 vCore of Azure SQL Managed Instance or Azure SQL VM under AHB. A 16-core on-premises SQL Server Enterprise deployment (8 physical cores × 2 with minimum licensing) provides 16 AHB vCore credits for Azure SQL. The on-premises deployment must be decommissioned, or the 180-day concurrent use right must be in effect for a legitimate migration period. AHB rights are managed through Azure Policy — ensure your Azure team is actually applying AHB to qualifying instances, as we regularly find clients with AHB-eligible workloads paying full pay-as-you-go rates due to policy misconfiguration. For related context: Microsoft Azure Hybrid Benefit: Maximize Your Savings.
On-Premises vs Azure: The Total Cost Decision Framework
The on-premises vs Azure SQL decision cannot be made on licence cost alone. The full cost comparison must include infrastructure costs (server hardware, data centre space, power, cooling, network), operational costs (DBA time, patching, backup management, DR testing), and the capital cost of maintaining hardware refresh cycles on an on-premises SQL estate. For most enterprises, the Azure SQL total cost of ownership is competitive with on-premises over a 3–5 year horizon once operational costs are included — particularly for Managed Instance deployments where AHB reduces the SQL licence premium.
The primary drivers that favour retaining on-premises SQL Server are: very high core-count workloads where the per-vCore Azure pricing exceeds the fully depreciated cost of owned hardware; latency-sensitive applications requiring sub-millisecond database response; and data sovereignty requirements that preclude cloud hosting. For most general-purpose enterprise SQL workloads, the combination of AHB, Reserved Instances for stable workloads, and operational cost savings from PaaS management makes Azure SQL Managed Instance the more economical long-term position.
Negotiating SQL Server in Your Microsoft EA
SQL Server is included in Microsoft Enterprise Agreements as a server product, with EA pricing typically delivering 15–25% discounts against list price for standard EA tier accounts. Key negotiating levers include: Software Assurance inclusion (SA is required for AHB rights and for version upgrade entitlement — its value must be assessed against the benefits consumed); commitment volume (higher SQL Server core commitments attract steeper discounts); and Azure SQL consumption commitments that can be cross-leveraged against on-premises pricing discussions.
One frequently overlooked negotiation opportunity is the SA step-down: if your on-premises SQL Server estate is stable and you are not migrating to Azure in the EA term, the value of SA (at typically 25% of licence cost per year) may not justify the cost. A documented assessment of SA benefits consumed — version upgrades, training, Extended Security Updates, AHB — versus SA cost allows a credible discussion with Microsoft about SA scope or alternatives. For the full Microsoft EA negotiation framework: Microsoft EA Negotiation: The Complete Guide for 2026. For licensing governance tools: Microsoft EA Guide.