The bigger one is the bill you have not been sent yet. Most SQL Server estates drift out of licensing compliance with no intent to cheat, and the gap only crystallises when someone audits it. We help you find your real position first, privately, while it is still cheap to fix.
Two different problems live in your SQL Server licensing, and only one of them is urgent. The first is over-provisioning. Cores you pay for and do not use. That is money already spent, worth recovering, and it reads as housekeeping. The second is the one that should reach your board. Under-licensing is an unbooked liability. The estate that runs fifty instances and is entitled to twelve has a gap, and the day it is audited that gap is settled at list price, with no discount, usually backdated, often with Software Assurance reinstated on top. Remediating a quarter-paid estate can cost well over four times the current bill. It does not appear on any report until the demand arrives.
None of this requires anyone to have cut a corner. The liability builds quietly, through the normal way SQL Server gets deployed:
- Passive and DR replicas assumed free. A failover or DR copy is only free with active Software Assurance on the primary, and only for one passive replica. The second one is licensable, and most estates have never checked.
- Virtual machine mobility. When a SQL VM can move across a cluster, Microsoft’s position is that every physical core on every host it could land on needs a licence. A ten-server reality becomes a whole-cluster liability the moment that is switched on.
- Edition creep. An Enterprise-only feature quietly running on a Standard licence. Transparent Data Encryption, the heavier Always On setups, partitioning, online index rebuilds. One ticked box, a compliance gap.
- Dev, test, and zombie instances. Spun up for a project, never decommissioned, often holding a copy of production, never counted.
- Small VMs under the minimum. SQL Server licenses a minimum of four cores per instance. A fleet of two-core VMs is quietly under-licensed against that floor.
Here is the part a CFO acts on. A recovered or avoided licensing cost is near pure margin. At a ten percent net margin, a dollar you stop spending is worth about ten dollars of sales you did not have to win. An avoided true-up is cleaner still. A seven-figure exposure that never crystallises is basis points of net income protected, the kind of number that belongs on a board slide. The licence bill is a cost line. The liability behind it is a risk line, and risk is the board’s job.
So the question is not whether you are overpaying. It is whether you know your real position, across every instance, before anyone outside this building does. Most organisations cannot answer that without going to ask someone, and the honest answer is usually no. That is not a failing. It is the normal state of an estate nobody has reconciled. It is also entirely knowable, on a calm afternoon, on your terms.
Where does yours sit?
A free, read-only 15-minute SQL Server health check now surfaces the licensing signal alongside the rest: edition against workload, core counts, and versions past support. No install, no obligation, and nothing leaves your control. You get a graded plain-English report you can take to your finance team. If your position is clean, you have that in writing for the next renewal. If it is not, you found out quietly, while it is still cheap to fix.
The proof: NZ$50M+ in client SQL Server licensing eliminated, about $7M a year. 20,000+ assessments. Worst single licensing leak seen around 95%. 17 compliance frameworks. New Zealand based, established 2018. SQL Server is all we do.
Want to know if this is sitting in your estate? We run a read-only check and hand you a graded report in plain English.
Get your free health check