SQL Server 2022 price and licensing. What drives the cost beyond the list rate.

SQL Server 2022 is licensed per core or by Server plus CAL. The edition, the core count and Software Assurance decide the real cost far more than the list rate, and each can be checked before you renew.

How much does SQL Server 2022 cost?

At Microsoft's published list price, SQL Server 2022 Enterprise costs $15,123 per two core pack, or $7,561.50 per core, and Standard costs $3,945 per two core pack, or $1,972.50 per core. Standard is also sold as a $989 server license plus a $230 Client Access License for every user or device.

Your price level under an Enterprise Agreement or CSP will differ, but the gap between the editions holds at every level. That is why the edition you pick changes the bill more than the licensing model does.

What does the four core minimum mean in practice?

You license at least four cores for every physical processor and for every virtual machine, whatever the hardware actually has. A two vCPU virtual machine running Standard therefore costs the same two packs as a four vCPU one, $7,890 at list.

Licenses are sold in two core packs, so a six core VM needs three packs. Once assigned to a server, a license must stay there for at least 90 days, which limits how often you can shuffle cores between hosts to cover a peak.

When does pay as you go beat a perpetual license?

Pay as you go wins when a workload will be gone within about two years. A hypothetical four core Enterprise VM for a migration project costs $1,096 a month at $274 per core, or $13,152 a year. Two Enterprise packs cost $30,246 up front, so the hourly route stays cheaper for roughly 27 months.

Add Software Assurance to the perpetual side and the crossover comes later still, because pay as you go already includes those rights.

Is per core or Server plus CAL cheaper for SQL Server 2022?

Per core is cheaper for large, external or hard to count user populations, and Server plus CAL is cheaper when a small, named group uses the database. Per core covers unlimited users. Server plus CAL charges a low server fee plus a CAL for every user or device that touches the instance.

At list, four Standard cores cost $7,890. The same server under Server plus CAL costs $989 plus $230 per head, so the lines cross near 30 users, and near 64 users on eight cores.

Does middleware reduce the number of CALs you need?

No. Microsoft's multiplexing rule says that hardware or software which pools connections does not reduce the CAL count. A user who reaches SQL Server through an application server, a web front end or an integration layer still needs a CAL, even if the database sees a single service account.

This rule decides more CAL disputes than any other clause in the product terms. If you cannot name every person and device behind the middleware, including customers or suppliers who log in, you are a per core customer.

Why should the CAL breakeven cover all your servers together?

One CAL covers a user or device on any number of licensed SQL Servers, provided the CAL is the same version as the server software or newer. The 30 user breakeven therefore only holds for a single server. Take a hypothetical finance team of 45 named users who work across three four core Standard instances.

A per server test would put each instance on per core, because 45 is above 30. Across the three servers, Server plus CAL is $10,353 cheaper. Rerun the comparison whenever headcount or the server count changes, because a group can also outgrow the combined breakeven.

When is SQL Server Enterprise worth 3.8 times Standard?

Enterprise is worth its premium only when an instance uses a feature Standard lacks, however important the workload. SQL Server 2022 Standard runs the full engine, capped at the lesser of four sockets or 24 cores and 128GB of buffer pool memory per instance, with basic availability groups of two replicas and one database.

Which SQL Server features actually require Enterprise?

• Memory above 128GB per instance. Standard caps the buffer pool; Enterprise goes to the operating system maximum.
• Advanced availability groups. Up to eight secondary replicas, four of them synchronous alongside the primary, and more than one database per group.
• Online index operations. Online and resumable index create and rebuild are Enterprise only, which matters for systems with no maintenance window.
• More than 24 cores in one instance. Standard stops there on SQL Server 2022.
• Unlimited virtualization. With Software Assurance, licensing every physical core of a host with Enterprise covers any number of VMs on it.

Transparent data encryption is often quoted as an Enterprise reason, but Standard has supported it since SQL Server 2019. If encryption is the only argument for Enterprise on an instance, that instance is a downgrade candidate.

What does an Enterprise to Standard downgrade return?

For a 16 core instance, the difference is $89,424 at list: eight Enterprise packs cost $120,984 and eight Standard packs cost $31,560. At a Software Assurance rate of about 25 percent a year, that also cuts roughly $22,356 from every annual SA payment, and nothing about the workload changes.

To test it, list the Enterprise only features in use on each instance. Where the list is empty, the instance usually dates from a project that was provisioned on Enterprise for an availability design that never shipped.

How is SQL Server 2022 licensed on virtual machines?

You either license each VM for its virtual cores, with a four core minimum per VM, or license every physical core of the host with Enterprise plus Software Assurance and run unlimited VMs. Since SQL Server 2022, licensing by individual VM requires Software Assurance or subscription licenses.

When does licensing the whole host win?

The host route wins once the VMs' combined licensable cores exceed the host's physical cores. On a 16 core host running Enterprise VMs of four vCPUs each, that happens past four VMs. Say the host runs six of them.

• Per VM. Six VMs at four cores is 24 core licenses, or 12 packs at $15,123, which is $181,476 at list.
• Per host. Sixteen physical cores is eight packs, or $120,984, with Software Assurance required for unlimited VMs.
• Difference. $60,492 in favor of the host, and every further VM on that host adds nothing.

This is the construct that makes dense private cloud SQL Server platforms affordable. The Windows Server and SQL Server practical guide works through more host scenarios, and the Hyper V licensing guide covers the hypervisor side of the same decision.

What does Software Assurance give a SQL Server buyer?

Software Assurance costs roughly 25 percent of the license price per year, and for most SQL Server buyers it is cheaper than the licenses it replaces. The rights that matter are these.

• Free passive failover replicas. For each licensed primary, one passive replica for high availability and one for disaster recovery on premises, plus one disaster recovery replica in Azure. Without SA, every passive replica needs full licenses.
• Licensing by VM. Per VM licensing on SQL Server 2022 requires SA or a subscription.
• License Mobility. The right to run licenses on an Authorized Mobility Partner's shared servers. Without it, a move into managed hosting can mean buying the licenses again.
• Azure Hybrid Benefit. Licenses with SA offset Azure SQL pricing, commonly 30 to 40 percent off the pay as you go rate for the same workload.

A passive replica stays free only while it is passive. It may run consistency checks, full and log backups and resource monitoring. Once it serves read only reports or any other client workload, it is active and needs its own licenses.

Should you drop Software Assurance once you are on the version you want?

Finance teams often propose dropping SA after the upgrade, assuming new version rights were its only benefit. We disagree for most SQL Server buyers, and the replica arithmetic on a 16 core Enterprise primary shows why.

• Keeping SA. About $30,246 a year, with one high availability and one disaster recovery replica covered.
• Dropping SA. Both replicas need full licenses, $241,968 at list, or about eight years of SA.

Dropping SA shows a saving on paper but converts every passive replica into a licensable instance, and it removes the per VM licensing right as well. Price the replicas and the VM layout under both options before the renewal, because Microsoft's audit scripts will price them for you later.

The renewal is where Software Assurance is won or lost, and the replica count is what decides it.

What have we found in SQL Server licensing reviews from 2024 to 2026?

Across roughly 30 to 40 Microsoft data platform reviews we ran between 2024 and 2026, model choice and edition mismatch caused most of the overspend. The pattern held for small and large companies alike.

Passive replicas licensed without Software Assurance added 20 to 40 percent to the SQL Server bill where we found them. Reconciling deployed cores, editions and replicas against entitlements pays back faster than any other Microsoft licensing work, and it is the evidence you need if a SQL Server audit arrives.

How do you check which SQL Server licenses you actually need?

Start with data from the servers themselves, then compare it with your entitlement records. These queries and views exist in every supported version.

• Edition and version. SELECT SERVERPROPERTY('Edition'), SERVERPROPERTY('ProductVersion') on each instance.
• Cores and sockets. sys.dm_os_sys_info returns cpu_count, socket_count and cores_per_socket as the instance sees them.
• Edition specific features per database. sys.dm_db_persisted_sku_features lists features that would block a move to a lower edition. It does not cover instance level features, so check availability groups and index maintenance jobs separately.
• Replicas. sys.availability_replicas shows every replica and whether secondaries accept read connections.

What will Microsoft say at a SQL Server renewal, and how should you answer?

Expect the conversation to push toward more Enterprise, more cloud and a quick signature. These are the lines we hear most, with the reply we recommend.

1. "Enterprise is the standard for production." Ask which Enterprise feature each instance uses. Show the feature check and propose Standard wherever the list is empty.
2. "Moving to Azure SQL removes the licensing problem." Ask for the Azure price with Azure Hybrid Benefit applied to the licenses you already own, next to the on premises renewal on the same core count.
3. "Order before quarter end to hold this price." Commit only to cores you have reconciled. A quarter end discount on cores you do not need costs more than list price on the right count.
4. "A licensing assessment will confirm you are covered." Agree the scope in writing and run your own reconciliation first, so any gap is found by you.

What changes with SQL Server 2025?

Pricing and the licensing model did not change. SQL Server 2025 kept the 2022 list prices, reaching volume licensing on November 18, 2025 and other channels in January 2026. Per core, Server plus CAL, the four core minimum and the SA rules all carry forward.

Does SQL Server 2025 change the edition decision?

Yes, in Standard's favor. SQL Server 2025 Standard raises the limits to the lesser of four sockets or 32 cores and to 256GB of buffer pool memory, double the 128GB ceiling in 2022. Instances kept on Enterprise purely for memory between those two figures become downgrade candidates on the new version.

A version change is also when Microsoft proposes subscriptions or Azure, so fix the edition mix and core counts first. Every error in the current licenses is repriced into whatever you sign next. The SQL Server licensing 2026 analysis covers the current price list in detail, and the SQL Server licensing pillar indexes the full topic.

What to do next

1. Count deployed cores against licensed cores. Do it per instance and per host, and include every passive replica. Surplus cores are savings, and missing ones are audit exposure.
2. Test every Enterprise instance against the Enterprise feature list. No feature in use means a Standard downgrade at the next true up or renewal, worth $89,424 per 16 core instance at list.
3. Price the passive replicas with and without Software Assurance before you renew or drop it. In most layouts we review, the annual SA fee is far smaller than licensing the replicas outright.
4. Rerun the CAL breakeven across all your CAL servers. User groups grow, and a group that has outgrown the breakeven is cheaper on per core.
5. Rightsize VMs before the true up. A VM built with eight vCPUs for a load test and never resized is licensed at twice the four core minimum. Move dense hosts to Enterprise host licensing.
6. Fix the licenses before the version or cloud conversation. Every misallocated core reprices into the next agreement. Our Microsoft practice runs this review with you, on your side of the table.

Frequently asked questions