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.
We're independent — we don't resell Microsoft licences and we're not a Microsoft Partner. The only thing we're optimising is your bill.
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 procurement call moves more money than everything else combined — and most estates are paying the 4x premium for features the workload never touches. 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. Right-size the edition to the workload and you stop paying four times over for headroom you do not use.
Five licensing rights most estates never use.
None of this is a loophole. These are ordinary terms of the licences you already hold — they just go unused because nobody's job is to know them.
Your passive failover node may already be free
If your primary carries Software Assurance or a subscription licence, a truly passive failover instance is covered by the primary’s licence — no separate purchase. Estates that licensed both nodes of an Always On pair are often paying twice for the same protection.
Developer Edition is free — use it for dev and test
Developer Edition carries the full Enterprise feature set and costs nothing, licensed strictly for non-production use. Every dev, test or UAT box running paid Standard or Enterprise is a leak with a one-line fix.
Azure Hybrid Benefit — stop paying for SQL twice in Azure
Core licences with Software Assurance can be re-used against Azure SQL and SQL on Azure VMs at a large discount to pay-as-you-go rates. Holding SA on-prem while paying full licence-included rates in Azure is double-paying.
Version downgrade rights
A current volume licence lets you run earlier versions of SQL Server. You rarely need to buy or keep legacy SKUs to support an old application — one current licence position covers the estate, old and new.
The SSRS / SSIS / SSAS separate-server rule
Reporting Services, Integration Services and Analysis Services are included with SQL Server — but the moment one runs on its own server, that server needs a full SQL Server licence. This cuts both ways: an unlicensed scale-out box is compliance risk; consolidating components back beside an engine you already license is a saving.
One 16-core cluster, two very different bills.
A common setup we find: a two-node Always On pair, 16 cores each, both nodes licensed for Enterprise "because that's how it was built." The workload is ordinary OLTP — no Enterprise-only features in use — and the secondary does nothing but stay in sync.
| As found | Right-sized | |
|---|---|---|
| Edition | Enterprise, both nodes | Standard, primary only |
| Cores licensed | 32 (16 × 2 nodes) | 16 — the passive node rides on the primary's Software Assurance |
| Indicative licence cost | ~NZ$400k | ~NZ$52k |
| Difference | ~NZ$350k — plus the annual Software Assurance percentage on top of it, every year | |
Indicative public list pricing, rounded — enterprise agreement, CSP and SPLA rates differ. The ratio is the point: Enterprise lists at roughly four times Standard per core, and an unnecessarily licensed passive node doubles whatever you chose.
Two decisions — the right edition, and not paying for the passive node — turn a ~NZ$400k position into ~NZ$52k for the same protection and the same performance. Neither requires new hardware, downtime, or a migration. It requires someone checking the workload against the licence, which is precisely what an audit does.
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.
Do I have to license my failover server?
Often no. If the primary is licensed with Software Assurance or a subscription licence, one truly passive failover instance is covered — it must do no work beyond staying in sync and waiting. If your passive node is licensed separately, that is usually money straight back. If the "passive" node serves read-only reports, it is not passive and does need licensing — worth checking before a true-up finds it.
Can we use Developer Edition for dev and test?
Yes — Developer Edition is free and has the full Enterprise feature set, licensed for non-production use only. The line that matters: if a workload serves the business (even reporting), it is production and needs a paid licence. Everything else — development, test, UAT, sandboxes — can and should run on Developer.
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.
Not sure where your own leak is?
Tell us what is going on. A senior DBA reads every message and points you at the right next step, even when that is not us. The free health check is read-only and puts a number on the overspend.