Answers

Should I license SQL Server per CAL or per core?

Illustration of software licensing, hardware and verification

Short answer

Per-CAL (Server+CAL) is cheaper when you have fewer than ~25 named users hitting the database — typically internal LOB apps. Per-core is required for any internet-facing app, for SQL Enterprise above 24 cores, and is usually cheaper above 25 users.

The longer explanation

The Server+CAL model licences one SQL Server plus a CAL for every user or device that reads, writes, or runs a query — direct or via middleware. It fits internal line-of-business apps with a knowable user count and no anonymous internet traffic.

Per-core licences every physical core (four-core minimum per socket) and covers unlimited users. It is required for internet-facing workloads, is the only model available for SQL Enterprise on servers above 24 cores, and typically wins the price race above 25–30 named users. If you virtualise, per-core also unlocks unlimited VMs per licensed host under SA.

People also ask

Why trust this answer

Written by licensing analysts who handle Microsoft Open, CSP and EU-resale transactions every day. We never paraphrase Microsoft contracts second-hand — every claim links to the actual EULA section, Microsoft Learn article, or court ruling it comes from. Found a discrepancy? Email research@licensevault.net and we will update the page within 48 hours.

Last updated: ← Back to all answers

Before choosing a licence

  1. 1. Check the exact edition, Windows or macOS compatibility and number of devices covered. A Windows-only key does not install Office for Mac.

  2. 2. Distinguish personal, commercial and server use. Virtual machines, shared devices and remote access can require additional licences.

  3. 3. Keep the invoice and licence terms. Check transfer rights and support dates: a perpetual licence does not mean perpetual security updates.

Successful activation alone does not prove permission for every use. The applicable Microsoft licence terms take precedence.