Answers
Should I license SQL Server per CAL or per core?
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
Is buying an OEM key online legal?
Yes in most countries — Microsoft sells OEM keys to system builders, and reselling unused, unbound OEM keys is permitted in the EU under the UsedSoft v Oracle ruling (CJEU C-128/11). In the US, OEM keys are legal once detached from the original system as part of a single transfer.
What's the difference between Office 2024 and Microsoft 365?
Office 2024 is a one-time purchase that locks the apps at their October 2024 version forever. Microsoft 365 is a subscription that includes the same apps plus 1 TB OneDrive, monthly feature updates, Outlook with email hosting (Business plans) and Copilot eligibility — but stops working when you cancel.
How many PCs can I install one Office licence on?
Perpetual Office (2021/2024 Home & Student / Home & Business / Pro) activates on exactly one PC and is transferable to a new PC if you uninstall on the old one. Microsoft 365 Personal allows install on unlimited devices but sign-in on five at a time; Family allows the same for six users.
How do I fix Windows activation error 0x80072F8F?
0x80072F8F is a TLS clock mismatch — Windows can't validate Microsoft's activation server certificate because the system date is wrong. Open Settings → Time & Language → Date & Time, enable 'Set time automatically' and 'Set time zone automatically', then re-run activation.
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