SQL Server license cost worked out on paper beside a server processor

SQL Server License Cost in 2026: What You Actually Pay

The SQL Server license cost is one of the hardest numbers in enterprise software to pin down. Microsoft publishes its prices, but almost nobody can work out what they will actually pay from them: the list price is quoted per two-core pack, the minimum you can buy is not the number of cores you have, one edition has a second licensing model the others don’t, and the free editions are good enough for more workloads than most people assume.

This page sets out the actual figures, the rules that change them, and the arithmetic for deciding which model is cheaper for your server. Prices are Microsoft’s US estimated retail (Open/ERP) figures for SQL Server 2025. Your reseller quote will differ, usually downward.

SQL Server license cost at a glance

EditionLicensingPrice
EnterprisePer core, 2-core pack$15,123
StandardPer core, 2-core pack$3,945
StandardServer license$989
StandardClient Access License (CAL)$230
DeveloperFree$0
ExpressFree$0

A four-core Standard server the smallest you can legally license costs $7,890. The same server on Enterprise costs $30,246. A sixteen-core Enterprise box is $120,984 before you have bought a single CAL, a support contract, or the hardware underneath it.

Those numbers are why this page exists.

The four editions, and the two that cost nothing

Express is free, permanently, including for commercial use. It caps each database at 50 GB — raised from 10 GB in the 2025 release — and limits the memory and CPU it will use. For a small line-of-business app, a website backend, or a departmental tool, Express is frequently the correct answer and people buy a license anyway because they assume free means crippled.

Developer is also free and is the full Enterprise feature set with no capacity limits. The catch is the license terms, not the software: it may be used for development and testing only. Running Developer Edition in production is a licensing violation, and it is one of the most common findings in a Microsoft audit.

Standard is the paid edition most organizations need. In SQL Server 2025 it will use up to 32 cores and 256 GB of buffer pool memory, both raised from the 2022 limits of 24 cores and 128 GB. It is also the only edition you can license through the Server + CAL model.

Enterprise removes the capacity ceilings and adds the high-availability and performance features — unlimited Always On replicas, online index operations, partitioning at scale, advanced compression. It is licensed per core only. Microsoft publishes the full edition and component comparison if you need to check a specific feature.

One edition has gone: Web is discontinued from SQL Server 2025. SQL Server 2022 is the last release that includes it, supported until January 2033.

How core licensing actually works

Three rules do most of the damage to a budget.

SQL Server license cost is calculated per processor core, not per server
SQL Server is licensed by the core, in packs of two, with a four-core minimum per processor.

You license every core in the processor, not the cores you use. If SQL Server runs on a physical machine, every core in every populated socket must be licensed, whether the database touches them or not.

Each physical processor needs at least four core licenses. A two-core CPU still costs you four cores. This minimum is per processor, so a dual-socket server with two six-core CPUs needs twelve core licenses, not eight.

Licenses are sold in packs of two. You cannot buy an odd number, and you cannot buy one.

Put together: the floor for any paid SQL Server deployment is four cores — two packs. For Standard that is $7,890. For Enterprise it is $30,246. Microsoft’s own compute capacity limits by edition set out what each edition will actually use once you have licensed it.

Server + CAL: when it is cheaper, exactly

Standard edition can instead be licensed by buying one server license at $989 and one Client Access License at $230 for every user or device that connects. Enterprise cannot be licensed this way at all.

Most guidance on this says “Server + CAL suits smaller user counts” and leaves it there. The break-even is calculable, and it depends entirely on how many cores the server has:

Server coresPer-core costEquivalent in CALsBreak-even users
4 (minimum)$7,890$989 + 30 × $23030
8$15,780$989 + 64 × $23064
16$31,560$989 + 133 × $230133
24$47,340$989 + 201 × $230201
32$63,120$989 + 270 × $230270

Read it this way: on a modest four-core server, Server + CAL stops being the cheaper option at about thirty users. On a thirty-two-core server you would need more than two hundred and seventy users before per-core licensing wins.

Two things flip the decision regardless of the arithmetic. If the database is internet-facing and you cannot count the users, per-core is the only workable model. And if you expect to grow past the user count in a year or two, buying CALs you will have to replace is a false economy.

Virtualization changes the math

License the individual virtual machine and you pay for the virtual cores assigned to it, with the same four-core minimum per VM. That is usually cheapest for one or two SQL VMs on a shared host.

License the physical host instead all its cores, on Enterprise, with Software Assurance — and you may run unlimited SQL Server VMs on that hardware. For a dense virtualization cluster this is dramatically cheaper per instance, which is why hosting providers and large shops do it. The entry cost is high enough that it rarely makes sense below roughly half a dozen SQL VMs per host.

Standard edition’s virtualization rights are narrower: you get VMs equal to the number of cores you have licensed.

The costs that are not on the price list

Software Assurance. It is what buys you version upgrades, license mobility between servers, and the host-level virtualization rights above. It is priced as a recurring annual percentage of the license cost, and over a typical hardware lifetime it can approach the license itself. Without it, you are buying a perpetual license for one specific version and one specific server.

The four-core minimum on small machines. A two-core VM is billed as four. Consolidating two small two-core instances onto one four-core instance halves the license cost for the same work.

Passive replicas. A standby server is only free if it is genuinely passive and you hold Software Assurance. Reporting off the secondary makes it an active instance and it must be licensed.

Azure Arc pay-as-you-go, if you go that route, runs roughly $73 per core per month for Standard and $274 per core per month for Enterprise. On a sixteen-core Enterprise server that is around $52,600 a year — which overtakes the perpetual license inside two and a half years, though it buys flexibility a perpetual license does not.

Which one do you actually need

Use Express if every database stays under 50 GB and the workload is light. It is free for commercial use and there is no license to buy.

Use Developer for every development, test, staging and training environment you run. It is free and it is the full Enterprise feature set. Never put it in production.

Use Standard with Server + CAL if the users are countable, internal, and fewer than the break-even number for your core count in the table above.

Use Standard per core if the database faces the internet, the user count is unpredictable, or you have passed that break-even.

Use Enterprise only if you need a specific capability it alone provides — more than 32 cores or 256 GB, multiple readable Always On replicas, online index rebuilds at scale. The gap between Standard and Enterprise is roughly four times the price per core. It is worth being honest about whether the features justify it, because most deployments that run Enterprise do not use anything Standard lacks.

Before you buy from anyone

SQL Server keys are sold across a wide price range, from a few hundred dollars to full list. Know what you are buying.

A volume license bought through a Microsoft reseller is what an audit expects to see. It is documented against your organization, and it is the only thing that makes per-core and Server + CAL entitlements defensible.

A single-server product key is a different product. It activates an installation. For a small business running one server, a lab, or a self-contained workload, that may be all you need. It is not a substitute for a per-core volume agreement if you are an organization large enough to be audited, and anyone telling you otherwise is selling you a problem for later.

If you are not sure which you need, the test is simple: would you be able to produce licensing paperwork if Microsoft asked for it next year? If the answer matters to you, buy the volume license.

Frequently asked questions

How much does a SQL Server license cost?

A four-core Standard license, the minimum paid deployment, is $7,890 at Microsoft’s estimated retail price. Enterprise for the same four cores is $30,246. Standard can alternatively be licensed at $989 per server plus $230 per user or device.

Is SQL Server free?

Two editions are. Express is free for commercial use with a 50 GB limit per database. Developer is free and feature-complete but licensed for development and testing only.

What is the difference between Standard and Enterprise?

Standard caps at 32 cores and 256 GB of memory and offers basic high availability. Enterprise removes those ceilings and adds advanced availability, performance and security features. Enterprise costs roughly four times as much per core.

Do I have to license every core in the server?

Yes. Every core in every populated socket must be licensed if SQL Server runs on that machine, with a minimum of four core licenses per physical processor, sold in two-core packs.

Is Server + CAL cheaper than per-core licensing?

It depends on your core count. On a four-core server the two models cost the same at about thirty users. On a sixteen-core server the crossover is around a hundred and thirty-three users. Below the crossover, Server + CAL is cheaper.

Can I run SQL Server Developer Edition in production?

No. The software is unrestricted but the license permits development and testing only. Production use is a licensing violation and a common audit finding.

Leave a Reply

Your email address will not be published. Required fields are marked *