SQL Server Core vs Server+CAL Licensing: Complete Comparison

SQL Server offers two fundamentally different licensing models: core-based and Server+Client Access Licence (Server+CAL). Choosing the wrong model can cost enterprise buyers hundreds of thousands of pounds in unnecessary licensing fees — a mistake we identify in approximately 18% of SQL Server audits.

This guide provides a complete comparison of both models, explains the break-even calculation that determines which model saves money, clarifies the edition constraints that limit your options, and covers the CAL counting rules that catch most enterprises in compliance failures. By the end, you will understand which model applies to each of your SQL Server deployments and how to use that knowledge in renewal negotiations.

Model Overview: Core vs CAL

SQL Server's two licensing models serve different deployment patterns. The correct model depends on the nature of the application, the size of the user population accessing it, and the SQL Server edition you choose to deploy.

Per-Core Licensing Model

Per-core licensing charges for the physical processor cores (or virtual cores) running SQL Server. It is required for most enterprise deployments and offers unlimited user access with no per-user licensing cost. Key characteristics:

• Calculation basis: Physical cores in the host server or virtual cores in a virtual machine
• Minimum 4 cores per processor: Even if your processor has fewer than 4 cores (rare in modern hardware), you pay for a minimum of 4 core licences per processor
• Minimum 2 processors per server: All servers are licensed for a minimum of 2 processors, regardless of actual processor count
• No CAL requirement: Users and devices access the server without requiring individual Client Access Licences
• Supports all editions: SQL Server Standard and Enterprise both use per-core licensing
• Sold in 2-packs: Core licences are priced and sold in 2-core packs

Server+CAL Licensing Model

Server+CAL licenses the SQL Server instance itself with a single server licence, then requires one Client Access Licence (CAL) for each user or device that accesses the database. This model is cost-effective only for small, closed environments with well-defined user populations.

• Two components: A single server licence plus one CAL per user or device
• Standard edition only: Server+CAL is not available for SQL Server Enterprise edition — this is a critical constraint
• Universal CAL requirement: Every user or device that accesses SQL Server requires a CAL, including indirect access through a web application or middle-tier service
• User-based scaling: Unlike per-core, CAL costs scale with user count, not with infrastructure capacity
• Cost grows with adoption: Any increase in the number of accessing users increases the licensing cost, making it unsuitable for growing applications

Break-Even Analysis: When to Use Each Model

The break-even point — the user count at which per-core licensing becomes cheaper than Server+CAL — is the critical decision threshold. Above break-even, per-core is always more cost-effective. Below it, Server+CAL can save money.

Current Pricing Example (2026)

At current list pricing:

• Server+CAL: ~£3,500 server licence + ~£180 per CAL annually
• Per-core (Standard): ~£3,960 per 2-core pack (for an 8-core server = £15,840 initial cost)
• Per-core (Enterprise): ~£14,600 per 2-core pack (for an 8-core server = £58,400 initial cost)

The break-even calculation shifts these variables: server processor count, CAL count, and whether you deploy Standard or Enterprise edition. A typical calculation for an 8-core Standard Edition server:

In this example, break-even occurs around 60–70 users. Below that, Server+CAL is less expensive. Above it, per-core saves money. The break-even threshold changes if the server has more or fewer cores — a 16-core server increases per-core cost and shifts the break-even higher.

CAL Counting: The Compliance Risk Zone

Server+CAL licensing failures occur almost entirely due to misunderstanding CAL counting rules. One compliance error:

• Counting "users" instead of "CALs": If 20 users all access the SQL Server during business hours, you need 20 CALs — not "1 CAL per shift" or "1 CAL per person per week"
• Ignoring indirect access: A web application or mobile app that queries SQL Server means every end user of that application requires a CAL. This is "indirect access" and is the most common audit finding.
• Forgetting about reporting tools: Business intelligence tools, reporting services, and analytics platforms that read from SQL Server all generate CAL obligations for their users
• Contractor and vendor access: Third-party users accessing SQL Server (support engineers, consultants, vendor applications) each require CALs
• System and service accounts: Some organizations incorrectly assume service accounts do not require CALs — they do, if they are used for business processing

In a 2025 audit we worked on with a UK financial services firm, they believed they had correctly licensed 150 CALs for their SQL Server database. Their actual user count was 340 — including 85 indirect users (loan officers accessing data through a reporting portal) and 105 contractor users (external auditors and systems integrators with database access). The true obligation was 340 CALs. The under-licensing exposure was £28,800.

Edition Constraints: Why Enterprise Buyers Often Get Forced to Per-Core

SQL Server Standard and Enterprise editions have different licensing options. This asymmetry is one of Microsoft's most effective commercial levers in licensing negotiations.

This constraint has a direct commercial impact. If you are considering SQL Server Enterprise edition for specific technical capabilities (advanced indexing, partitioning, compression, or high-availability features), you are forced into per-core licensing. You cannot use Server+CAL to reduce costs. This is why many enterprises discover that the total cost of ownership for Enterprise edition includes a hidden per-core licensing floor.

For renewal negotiations, this creates a leverage point: if your application genuinely requires Enterprise features, you are locked into a per-core cost model. If it does not, negotiating a Standard Edition deployment (with Server+CAL as an option) can create cost reduction leverage during talks.

When to Use Each Model: Decision Framework

Use Per-Core Licensing When:

• The application user base exceeds 60–80 users (the break-even threshold for most configurations)
• You anticipate user growth over the EA term — CAL costs will grow with headcount
• The application has indirect access through web applications, APIs, or BI tools
• You are deploying SQL Server Enterprise edition (no other option available)
• The application is internet-facing or involves third-party user access (where CAL counting becomes impractical)

Use Server+CAL Licensing When:

• The application serves fewer than 30 users and has no realistic growth trajectory
• The user population is completely closed and well-defined (not public-facing, not third-party exposed)
• You are deploying SQL Server Standard edition
• You can reliably forecast the user count for the entire EA term (CALs do not scale well with changing headcount)
• The cost comparison clearly favors CAL over per-core for your specific configuration

Renewal Negotiation Strategy: Using Model Selection as Leverage

The per-core vs Server+CAL decision creates negotiation leverage in EA renewals.

Scenario 1: You Are Currently on Server+CAL

If you are approaching renewal and your user count has grown significantly since the EA began, you have a powerful negotiation position: Server+CAL is no longer the cost-effective model. You can propose switching to per-core licensing and position it as a cost-management strategy (which it is for your situation). This gives you leverage to:

• Request a lower per-core price to offset the Server+CAL price you are leaving behind
• Consolidate multiple small SQL Server instances (currently justified under CAL model) into larger per-core-licensed instances, creating consolidation savings
• Use the model switch as a bargaining chip in multi-product EA negotiations

Scenario 2: You Are Currently on Per-Core

If you are currently using per-core licensing and your deployment has specific characteristics (Standard Edition only, small user base), you can model the Server+CAL alternative and present it to Microsoft as a reduction lever. Even if the CAL model is not financially superior in your case, presenting it as an option can:

• Demonstrate that you have analyzed alternatives and will move to a lower-cost model if pricing is not competitive
• Create perceived flexibility that makes you more likely to accept a renewal offer

Key Takeaways

• Break-even matters: Calculate your specific break-even threshold. For most enterprises, it is in the 60–80 user range
• CAL counting is a minefield: If you are considering Server+CAL, ensure you understand indirect access and third-party user obligations
• Edition locks your options: Enterprise edition forces per-core licensing. This is a cost constraint to consider when evaluating editions
• Renewal timing is critical: If your user base has grown since the last EA, you have a model-switching opportunity to negotiate from
• Audit exposure differs: Per-core under-licensing is common but simpler to remediate. CAL under-licensing is devastating and harder to defend in audit response