SQL Server licensing — the most-audited Microsoft product.

Enterprise vs Standard — and the feature gates that drive the choice.

SQL Server Enterprise Edition lists at $15,123 per 2-core pack ($7,562 per core); Standard Edition lists at $3,945 per 2-core pack ($1,973 per core). The 3.8x price differential between the editions is one of the most expensive licensing decisions in the Microsoft stack. The feature gates that justify Enterprise: Always On Availability Groups with more than one secondary, online indexing, partitioning, columnstore indexing for very large datasets, change data capture, Polybase external tables, and the unlimited virtualization rights bundled with SA.

The most common Enterprise over-licensing error is using Enterprise on workloads that do not use Enterprise-specific features. Customers frequently inherit Enterprise licensing from a legacy deployment, then continue paying Enterprise rates on databases that would run perfectly well on Standard. The remediation requires a feature-by-feature inventory of which databases use which Enterprise-gated features. In our experience, 25–40% of Enterprise core licences at typical enterprises could be down-edition to Standard.

Core licensing minimums

SQL Server has a minimum of 4 cores per physical processor; servers with fewer than 4-core processors must still be licensed at 4 cores per processor. Cores are licensed in 2-core packs. Server+CAL licensing — the legacy alternative model — is available for Standard Edition only and is appropriate for environments with fewer than 75 users per server; above 75 users, core licensing is more cost-effective.

Per-VM, per-host and the unlimited rule — the rules that change the bill.

SQL Server virtualization has three patterns. Per-VM licensing: licence each VM at the cores assigned to that VM (minimum 4 cores per VM). Per-host licensing: licence all physical cores on the host, then run unlimited VMs on that host — only available for Enterprise Edition with Software Assurance. Per-host with no SA: not permitted; per-host requires SA.

The decision pattern: per-VM is more cost-effective when running fewer than 4–5 SQL VMs on a host; per-host is more cost-effective when running many SQL VMs on a single host. The catch is the SA requirement on per-host — customers without SA must license per-VM, which can be punishing on heavy-virtualization estates. The break-even calculation should include the cost of SA.

Disaster recovery rights

SQL Server with Software Assurance includes "fail-over rights" — a passive secondary replica does not require its own licence, provided it is truly passive (not serving any read or write workload). The 2019 contract update narrowed this benefit: customers without SA must license passive replicas; customers with SA receive one passive replica licence per active production licence. The rule is a frequent audit finding because passive replicas are frequently configured to serve read traffic for reporting, which voids the passive status and triggers a licensing exposure.

Azure Hybrid Benefit for SQL — the deepest discount in the Microsoft stack.

Azure Hybrid Benefit applied to SQL Server is the single highest-leverage Microsoft cost optimisation. SQL Server Enterprise core licences with active Software Assurance can be applied to Azure SQL VMs, Azure SQL Managed Instance and Azure SQL Database with a discount on the SQL component of the Azure bill of 55–80%. The savings compound with Azure Reservations — AHB plus 3-year Reservation typically reduces total Azure SQL cost 70–85% versus pay-as-you-go.

The dual-use rule permits a SQL Server licence with SA to support an on-premises workload and an Azure workload simultaneously during a 180-day migration window. Beyond 180 days, the licence must be assigned to one workload or the other. The 180-day rule is the standard pattern for cloud migration; it is also frequently missed when migrations slip.

Audit triggers for SQL Server

The SQL Server audit triggers most frequently observed: deploying SQL Server on hosts where the core count was not properly reconciled, configuring passive replicas to serve read traffic, running SQL Server in production environments without CAL coverage, using Enterprise-edition features (partitioning, columnstore) on Standard-edition licences, and failing to validate the SA status before claiming AHB. Each of these patterns shows in the Microsoft inventory and ML Inventory tool data.

For SQL Server estates above $500K annually, independent software license optimization across editioning, virtualization and AHB typically captures cost reduction equal to four to twelve times the advisory fee.