SQL Server Licensing Audit: A New Zealand Guide to Cutting Costs

A SQL Server licensing audit checks every instance you run: edition, cores, Software Assurance, and what each one is actually doing. Then it finds the licences you’re paying for and don’t need. Most estates we see are over-licensed. We usually take 20 to 40% off the SQL bill, sometimes more.

The worst we have ever seen was a 95% leak. Almost the whole bill was for licences nobody needed.

Across the assessments we’ve run, clients have stopped paying for over NZ$50 million in licences they didn’t need. That’s about $7 million a year.

Over NZ$50 million in SQL Server licensing taken off client bills. About $7 million a year. Across 20,000+ instance assessments.

What the audit actually checks

Six things decide your SQL bill. We go instance by instance and check each one.

Edition. Enterprise costs about four times Standard. Are you running it on a workload that never touches an Enterprise feature?
Cores. Physical core counts, the four-core-per-processor minimum, and how your VM density changes the maths.
Software Assurance. You either use the benefits you pay for or you leave them on the table. Licence mobility, failover rights, pay-as-you-go.
Passive and DR replicas. Some need a licence. Some don’t. It depends on your SA, and people get this wrong both ways.
Virtualisation. Per VM or per host. Live Migration and vMotion spread licences across hosts when nobody’s watching.
Idle servers. Dev, test, decommissioned boxes, old replicas. Still licensed. Still on your bill. Nobody using them.

Where the money actually leaks

Enterprise you don’t need. This is the big one. Most over-spend lives here. An instance gets built on Enterprise because the last project did it that way, and nobody revisits it. If the workload doesn’t use an Enterprise-only feature, Standard is usually compliant and costs a quarter as much.

Licensing a whole host for two VMs. Without SA and the right counting model, virtualised SQL goes one of two bad ways. You pay for every core on the host, or you under-license and carry a compliance risk into your next Microsoft true-up. The audit works out which model is cheapest for your setup, and whether it’s compliant.

Servers nobody uses. Decommissioned boxes, dev and test, passive replicas left running. They keep drawing licences months after the work stopped. Finding them is the fastest money you’ll get back.

Enterprise or Standard: the decision that moves the most money

Enterprise lists at roughly four times Standard, per core. So this one call moves more money than everything else in the audit 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. We map what you actually use against the edition that requires it. You pay for the tier the workload needs, not the tier it got installed with.

How the audit runs

We inventory every instance, edition and core count. For most sites this is the first time anyone’s had an accurate list.
We map the features in use against the edition that requires them.
We reconcile that against your Microsoft licensing and Software Assurance.
We model the cheapest compliant setup: edition changes, consolidation, the SA calls.
You get a prioritised plan with a dollar figure against each change. Biggest wins first.

Is it worth it?

Is it your policy to pay Microsoft for cores you don’t run? No. So we go and find them. One mis-sized Enterprise instance can cost tens of thousands a year. The audit usually pays for itself on the first finding. It cuts the other way too. Under-licensing is a real exposure when Microsoft runs a true-up, and it’s a lot cheaper to fix on your terms than on theirs.

Frequently asked questions

How much can it save?

Usually 20 to 40% of your SQL licensing spend. Over-provisioned estates save more. The money comes from right-sizing editions, retiring idle instances, and fixing virtualisation licensing.

How long, and will it touch production?

A few days to a week. It’s read-only. We look at configuration and usage metadata. We change nothing on your servers, so there’s no production impact.

Does it cover Azure SQL and Managed Instance?

Yes. Cloud changes the model: vCore, Azure Hybrid Benefit, reserved capacity. The same right-sizing logic applies. If you already hold Software Assurance, Azure Hybrid Benefit usually finds more.

Do you only work with New Zealand businesses?

We’re New Zealand-based and work across New Zealand and Australia. The audit runs remotely, so where you are doesn’t matter.

Find out what you’re overpaying

We’ve run more than 20,000 SQL Server instance assessments and taken over NZ$50 million off client licensing. If you want to know what you’re overpaying, ask us for a licensing audit. We’ll show you the number before you commit to anything.