SQL Server is one of the most expensive things Microsoft sells, and one of the easiest to license wrong. The reason is that almost none of the cost is where people look. It is not in the number of databases, or the number of users, or even really the number of servers. It is in two decisions most companies make once and never revisit: which edition you run, and how you license the virtualization underneath it. Get those two right and the bill is reasonable. Get them wrong and you can pay several times over for capacity you never use, and not find out until a true-up asks you to write the check.
How does SQL Server licensing work?
SQL Server is licensed by the core. You count the physical cores on the server, or the virtual cores assigned to a VM, and license those. Core licenses are sold in packs of two, with a minimum of four core licenses per physical processor or per VM. There are two editions, Standard and Enterprise, and Standard can alternatively be licensed under the older Server plus CAL model. The edition and the core count are what set the bill, not the number of installations.
That last point is where the intuition breaks. Adding another database to an existing licensed server costs nothing in licensing terms. Moving that same workload onto more cores, or onto Enterprise when Standard would have run it, costs a great deal. The model rewards knowing exactly what runs where, and punishes estates that have lost track.
What is the cost difference between SQL Server Standard and Enterprise?
On Microsoft’s list pricing, Enterprise runs about four times the cost of Standard per core, roughly $15,000 per two-core pack against about $3,900, and Enterprise is only available under core-based licensing. For most workloads the choice of edition moves the bill more than any discount you negotiate, because it multiplies across every core.
This is the single highest-leverage question in a SQL estate. Enterprise exists for a reason, and some workloads genuinely need its high-availability and scale features. But a large share of SQL overspend is Enterprise sitting on workloads that Standard would have run perfectly well, bought once during a project when nobody wanted to risk under-provisioning, and never revisited. Every one of those cores is being billed at four times the rate it needed to be. A discount negotiated on top of the wrong edition is a smaller number on a bill that should not exist.
How is SQL Server licensed in a virtual environment?
You have two options, and the gap between them is where the real money hides.
You can license the virtual cores assigned to each VM, with the same four-core minimum per VM. This suits a small number of SQL VMs on shared hosts.
Or you can license every physical core on the host, which then lets you run unlimited SQL VMs on that host. This usually wins once you are running SQL densely, and maximum-density and license-mobility scenarios require active Software Assurance.
The expensive mistake is the mismatch. License one busy SQL VM against every core on a modern host, and you can pay for sixty-four cores to run a workload that uses eight. License a dense host per-VM, and you pay the four-core minimum many times over. Neither is wrong as a rule. Both are wrong on the wrong estate, and the only way to know which you are is to look at how SQL is actually deployed against the hardware.
Are SQL Server failover and disaster recovery replicas free?
Only with active Software Assurance or subscription licenses. With Software Assurance you are entitled to free passive secondary replicas for high availability and disaster recovery, including a disaster recovery instance in Azure since SQL Server 2019.
This is the right most companies own and never claim. If your primary SQL licenses carry Software Assurance, the passive server sitting there for failover does not need its own licenses, and neither does the disaster recovery replica. But the moment Software Assurance lapses, or was never attached to those cores, every passive replica becomes fully licensable. A server the architecture team correctly stood up for resilience becomes, at audit time, a server the licensing team never paid for. Same box, very different conversation, and the difference is entirely whether anyone tracked the Software Assurance.
What is Azure Hybrid Benefit, and why does it matter?
Azure Hybrid Benefit lets you apply SQL Server core licenses you already own, with active Software Assurance or a subscription, to SQL Server running in Azure. It requires Software Assurance.
It matters because the alternative is paying twice. Without it, SQL you move to Azure is priced as if you owned nothing, on top of the on-premises licenses you already bought. With it, the licenses follow the workload. It is one of the more valuable Software Assurance rights and one of the most commonly forgotten during a cloud migration, because the migration is run by a cloud team measuring compute, not a licensing team measuring entitlements. The rights are sitting in the agreement. Someone has to remember to use them.
Where do companies most often overpay on SQL Server?
Three places, and they compound.
The wrong edition, meaning Enterprise where Standard would have done the job.
Full-capacity licensing of a virtualization host that a per-VM count would have licensed for less.
And unclaimed Software Assurance rights, especially the free passive and disaster recovery replicas.
Together these commonly account for 20 to 40 percent of a SQL Server bill. What they share is that none of them show up in day-to-day operations. SQL runs fine whether you licensed it well or badly. The gap only becomes visible when a SQL Server true-up or an audit forces someone to reconcile what is deployed against what is licensed, and by then the overpayment has usually been running for years.
How do you get SQL Server licensing right?
Before the true-up, not during it.
Match the edition to the workload. Go through the estate and find every Enterprise core carrying a workload Standard would run. This is almost always the biggest single number.
License virtualization to how SQL actually sits on the hardware. Per-VM where SQL is sparse, per-host where it is dense, and never the reverse.
Track Software Assurance against every SQL core. It is what turns passive replicas free, unlocks Azure Hybrid Benefit, and enables license mobility. Cores without it are cores paying full freight and forfeiting rights.
Reconcile deployed against licensed on your own schedule. The company that walks into a true-up with its own core count already built is negotiating. The one that does not is being told a number.
Where UMS fits
We spent years running audits for the software publishers, and SQL Server is one of the places we saw the most money left on the table, in both directions. On SQL Server optimization we rebuild the real core position, edition by edition and host by host, and hold it against what you are actually licensed for before Microsoft does the same math with a bill attached.
We are paid only from the savings we find. No savings, no fee. If a Microsoft true-up or renewal is anywhere on the horizon, give us 30 minutes before it lands.
Frequently asked questions
How does SQL Server licensing work? SQL Server is licensed by the core. You count the physical cores on the server, or the virtual cores assigned to a VM, and license those. Core licenses are sold in packs of two, with a minimum of four core licenses per physical processor or per VM. There are two editions, Standard and Enterprise, and Standard can alternatively be licensed under the older Server plus CAL model. The edition and the core count are what set the bill, not the number of installations.
What is the cost difference between SQL Server Standard and Enterprise? On Microsoft’s list pricing, Enterprise runs about four times the cost of Standard per core, roughly $15,000 per two-core pack against about $3,900, and Enterprise is only available under core-based licensing. For most workloads the choice of edition moves the bill more than any discount you negotiate, because it multiplies across every core. A large share of SQL overspend is Enterprise licensing sitting on workloads that Standard would have run.
How is SQL Server licensed in a virtual environment? You have two options. License the virtual cores assigned to each VM, with the same four-core minimum per VM, which suits a small number of SQL VMs. Or license every physical core on the host, which lets you run unlimited SQL VMs on that host and usually wins once density is high. Maximum-density and license-mobility scenarios require active Software Assurance. Licensing a busy VM the wrong way is one of the most expensive mistakes in the whole model.
Are SQL Server failover and disaster recovery replicas free? Only with active Software Assurance or subscription licenses. With Software Assurance you are entitled to free passive secondary replicas for high availability and disaster recovery, including a disaster recovery instance in Azure since SQL Server 2019. The moment Software Assurance lapses, those passive replicas become fully licensable, so a server you thought was free turns into a line on an audit.
What is Azure Hybrid Benefit for SQL Server? Azure Hybrid Benefit lets you apply SQL Server core licenses you already own, with active Software Assurance or a subscription, to SQL Server running in Azure, so you are not paying for the same cores twice. It requires Software Assurance. It is one of the more valuable Software Assurance rights, and one of the most commonly left unclaimed during a cloud migration.
Where do companies most often overpay on SQL Server? Three places. The wrong edition, meaning Enterprise where Standard would have done the job. Full-capacity licensing of a virtualization host that a per-VM count would have licensed for less. And unclaimed Software Assurance rights, especially the free passive and disaster recovery replicas. Together these commonly account for 20 to 40 percent of a SQL Server bill, and none of them show up until a true-up or an audit forces the math.
Source notes
- SQL Server 2022 editions comparison (Microsoft): the edition split between Standard and Enterprise and the core-based licensing model.
- Microsoft Volume Licensing Product Terms: the governing terms for core licensing, Software Assurance benefits, and virtualization rights.
- SQL Server free failover licensing (SAMexpert): the free passive replica entitlement and its dependence on active Software Assurance.
- SQL Server Enterprise per-core list pricing (Hakuna Matata Tech): current list pricing of about $15,123 per two-core Enterprise pack against about $3,945 for Standard, the basis for the roughly four times figure.
- UMS SQL Server optimization: the UMS service page for SQL Server licensing and audit defense.