English
Español
Français
Deutsch
العربية
Português
Italiano
Polski
SQL Server Standard is a workhorse for small and mid-sized businesses, but the moment you go to buy it you hit a wall: Microsoft sells the exact same edition under two completely different licensing models, and the price gap between them can be enormous. Pick the wrong one and you either overpay by hundreds of dollars or leave yourself out of compliance.
The good news is that the decision comes down to a single question about your users. This guide explains the two models — Per-Core and Server + CAL — in plain English, walks through two real-world cost examples, and shows you which retail key to buy so you get the legitimate license at the lowest legal price.
⭐ Key Takeaways
- SQL Server Standard can be licensed as Per-Core or Server + CAL; Enterprise is Per-Core only.
- Per-Core licenses every physical core (minimum 4 per instance, sold in 2-core packs), needs no CALs, and allows unlimited users.
- Server + CAL means one Server license plus a CAL for every user or device that accesses SQL Server — you do not license the cores at all.
- Server + CAL wins for a handful of known internal users; Per-Core wins for web apps and large or unknown user counts.
- SoftKeys sells genuine retail keys: SQL Server 2022 Standard for $85.99 and 2016/2019 Standard for $29.99.
The two licensing models
Microsoft offers SQL Server Standard under two models that produce identical software with identical features. The only difference is how you count and pay for it.
The Per-Core model charges you for the processing power of the server — specifically, every physical core the SQL Server instance can use. Users are irrelevant; you could have one person or a million, and the price does not change. The Server + CAL model flips that around: you pay a modest flat fee for the server software, then buy a small Client Access License (CAL) for each user or device that touches the database. Here the cores are irrelevant and the user count drives the cost.
Because these two models scale in opposite directions — one on hardware, one on people — the cheaper choice depends entirely on the shape of your deployment. One important limit up front: this flexibility only exists for the Standard edition. If you need Enterprise, your only option is Per-Core.
Per-Core explained
Under Per-Core licensing you count the physical cores available to the SQL Server instance and license all of them. Core licenses are sold in 2-core packs, and every instance carries a minimum of 4 cores even if the hardware has fewer. So a modern 8-core server needs eight core licenses (four 2-core packs); a small 2-core VM still needs the four-core minimum.
The payoff for licensing the hardware is that you never buy CALs and you can connect unlimited users. That makes Per-Core the correct — and often the only compliant — choice whenever you cannot count your users:
- Public or internet-facing databases where anyone on the web can reach the app.
- Customer-facing web applications, e-commerce sites, and SaaS backends.
- Any workload with a large, fluctuating, or genuinely unknown number of users.
The trade-off is cost predictability in the wrong direction: as your core count grows, so does the bill, regardless of how many people actually use the system.
Server + CAL explained
Under Server + CAL you buy one Server license for the machine running SQL Server, then one CAL for each user or device that accesses it. You do not license the cores, so the server’s processor count has no effect on price. You choose either User CALs (per named person, good when people use several devices) or Device CALs (per machine, good for shared workstations or shift workers).
This model shines when you have a small, well-defined group of internal users — the office staff who open a line-of-business app, an accounting team hitting a shared database, an internal reporting tool. Add up the people (or devices), buy that many CALs plus one server license, and you are done. The catch is that CAL costs rise with every user, so once the crowd gets large enough, Per-Core overtakes it.
| Per-Core | Server + CAL | |
|---|---|---|
| What you pay for | Every physical core on the server | One server license + one CAL per user/device |
| Do you count users? | No — unlimited users | Yes — one CAL each |
| Do you count cores? | Yes (min. 4, sold in 2-core packs) | No |
| Best for | Public / web apps, large or unknown user counts | Small, known number of internal users |
| Available on Standard? | Yes | Yes |
| Available on Enterprise? | Yes | No (Per-Core only) |
Two worked examples
The models are easiest to understand side by side. Consider two common scenarios.
Example 1 — A 5-person internal accounting team. Five staff open a desktop app that reads and writes to a SQL Server database on an 8-core office server. With Per-Core you would have to license all eight cores — four 2-core packs — even though only five people ever connect. With Server + CAL you buy one server license plus five CALs and ignore the cores entirely. The user count is tiny and fixed, so Server + CAL is dramatically cheaper. This is the textbook case for it.
Example 2 — A public e-commerce website. Your online store’s database is reached by every visitor who browses a product or places an order. You cannot count those users, they change constantly, and they are anonymous members of the public. Buying a CAL for each is impossible, so Server + CAL is not viable. You license the server’s cores instead — the 4-core minimum for a small VM, or all cores on a bigger box — and serve unlimited shoppers. Per-Core is the only correct choice here.
The pattern holds across almost every deployment: known internal headcount points to Server + CAL, while public or open-ended access points to Per-Core.
Which to buy and which version
Start with the users. If you can name everyone (or every device) that will touch the database and the number is small and stable, choose Server + CAL. If the database is web-facing or the audience is large or unpredictable, choose Per-Core and license the cores at the 4-core minimum or higher. If you have been told you need Enterprise edition, the decision is made for you — it is Per-Core only.
On the version question, buy the newest edition your applications and hardware support. SQL Server 2022 Standard is the current release with the longest support runway, better performance, and the latest security features — it is the right pick for a new build. If you are matching an existing environment, standardizing older servers, or working to a tight budget, a 2016/2019 Standard key covers the vast majority of production workloads at a fraction of the price. Both are genuine retail licenses below.
📦 Genuine SQL Server Standard Keys
Frequently Asked Questions
Is Per-Core or Server + CAL cheaper for SQL Server Standard?
It depends on your users. For a small, fixed group of internal users, Server + CAL is usually much cheaper because you only pay for one server plus a CAL each. For public or large user counts, Per-Core is cheaper and often the only compliant option.
How many core licenses does SQL Server Standard need?
You license every physical core the instance uses, with a minimum of four cores per instance. Core licenses are sold in 2-core packs, so an 8-core server needs four packs and a small server still needs the four-core minimum.
What is a SQL Server CAL?
A Client Access License grants one user or one device the right to access a licensed SQL Server. It is not installable software and does not run the server — it simply authorizes access under the Server + CAL model.
Do I need CALs if I license Per-Core?
No. Per-Core licensing covers unlimited users with no CALs required, which is exactly why it suits public and internet-facing databases where users cannot be counted.
Can I license SQL Server Enterprise with Server + CAL?
No. Enterprise edition is available under the Per-Core model only. The Server + CAL option exists solely for the Standard edition.
Should I buy SQL Server 2022 or an older Standard version?
Choose 2022 Standard for a new build — it has the longest support and newest features. Pick 2016/2019 Standard to match an existing environment or to save money, since it runs most production workloads at a much lower price.
Final thoughts
SQL Server Standard licensing looks intimidating, but it hinges on one honest question: can you count your users? A small, known headcount points to Server + CAL and the lowest possible cost, while public access or an open-ended audience points to Per-Core. Get that call right, buy a genuine retail key at the version you need, and you have a fully legitimate SQL Server deployment without paying enterprise-reseller prices.
