How to cut your SQL Server licensing bill.
Most SQL Server estates are over-licensed by 20 to 40%. The money leaks in a few predictable places, and once you find them you stop paying for them. Here is where it goes, and how to get it back.
Five places SQL Server licensing leaks.
Enterprise you do not need
The big one — most overspend lives here. Enterprise lists at roughly four times Standard per core. If a workload never touches an Enterprise-only feature, Standard is usually compliant and costs a quarter as much.
A whole host licensed for two VMs
Without Software Assurance and the right counting model, virtualised SQL goes one of two bad ways: you license every core on the host, or you under-license and carry a compliance risk into your next true-up.
Idle servers still on the bill
Dev, test, decommissioned boxes, old replicas — still licensed, still drawing cost, nobody using them. Finding them is the fastest money you will get back.
Mis-counted cores
Physical core counts, the four-core-per-processor minimum, and how VM density changes the maths. People over-count and under-count, both expensively.
Software Assurance left on the table
Licence mobility, failover rights, pay-as-you-go — benefits you are paying for and not using. Used properly, SA often pays for itself; ignored, it is pure cost.
Enterprise or Standard.
Enterprise lists at roughly four times Standard, per core, so this one call moves more money than everything else combined. A few things genuinely need Enterprise: unlimited virtualisation, the heavier Always On setups, some large data-warehouse features. Plenty of ordinary OLTP databases need none of it, and got built on Enterprise because the last project did. Map what you actually use against the edition that requires it, and you pay for the tier the workload needs — not the tier it was installed with.
What people ask about cutting the SQL bill.
How much can we realistically save?
Usually 20 to 40% of the SQL Server bill, sometimes more. Over-provisioned estates save more. The money comes from right-sizing editions, retiring idle instances, and fixing virtualisation licensing. The worst single leak we have ever seen was 95% — almost the whole bill was for licences nobody needed.
Will checking touch production?
No. A licensing audit is read-only. We look at configuration and usage metadata, change nothing on your servers, and there is no production impact. It usually takes a few days to a week.
Does this cover Azure and Managed Instance?
Yes. Cloud changes the model — vCore, Azure Hybrid Benefit, reserved capacity — but the same right-sizing logic applies. If you already hold Software Assurance, Azure Hybrid Benefit usually finds more.
What does it cost to find out?
Start with the free, read-only health check — it shows you the shape of the overspend on one instance. A full licensing audit usually pays for itself on the first finding, and we show you the number before you commit to anything.