SQL Server 2022 Standard vs Enterprise

The two ceilings that actually force Enterprise

Standard is capped at the lesser of four sockets or 24 cores per instance, and 128 GB of buffer pool memory. The memory cap is the one that bites first: it covers the buffer pool only, so a 200 GB database on a 256 GB server will still thrash disk under Standard because SQL Server cannot cache more than 128 GB of pages.

Before assuming you have outgrown Standard, check what your instance actually uses. If your buffer pool is sitting at 60 GB with a healthy page life expectancy, more memory buys you nothing and Enterprise is a five-figure invoice for headroom you are not consuming.

• Run `SELECT cntr_value/1024 AS mb FROM sys.dm_os_performance_counters WHERE counter_name = 'Total Server Memory (KB)'` to see real usage.
• Page life expectancy consistently under 300 seconds with the buffer pool pinned at 128 GB is the honest signal that you are memory-bound.
• If one instance needs more than 24 cores, splitting into two Standard instances is often cheaper than one Enterprise instance — but only if the workload partitions cleanly.

High availability: what Basic Availability Groups do not give you

Standard includes Basic Availability Groups, and people routinely over-read what that means. A Basic AG covers exactly two replicas, exactly one database per group, and the secondary is not readable and cannot be backed up from. There is no read-scale, no multi-database failover consistency, and no automatic seeding across more than the pair.

Enterprise raises this to eight secondaries, readable secondaries for reporting offload, backups from secondaries, and availability groups spanning multiple databases that fail over together — which matters the moment an application writes across two databases in one transaction.

• Need reporting offloaded to a replica? That is Enterprise, or a separate licensed Standard server fed by log shipping.
• Two databases that must fail over together? Basic AGs cannot express that.
• A simple two-node failover cluster instance on shared storage is available in Standard and covers most single-site HA needs.

Maintenance windows: the hidden Enterprise tax

Online index rebuilds, online schema changes, and resumable index operations are Enterprise-only. On Standard, rebuilding an index takes the table offline for the duration. For a 24/7 system with a 300 GB table, that is not a licensing preference — it is the difference between a routine Tuesday and a scheduled outage.

If your maintenance window is generous, Standard plus `REORGANIZE` instead of `REBUILD` handles most fragmentation without the upgrade. If you have no window at all, price Enterprise against the cost of the outages you would otherwise take.

Per-core versus Server + CAL — the decision most buyers get wrong

Standard is the only edition still offered under Server + CAL. One server licence plus a client access licence for every user or device is dramatically cheaper for small user counts: a 16-core server under per-core licensing runs eight 2-core packs, while the same server under Server + CAL with 25 users is a fraction of that.

The catch is that Server + CAL caps you at 24 cores regardless, and every human or device touching the data needs a CAL — including indirect access through a web app or reporting layer, which is where audits find money. Multiplexing does not avoid CALs.

• Per-core: no CAL counting, required for public-facing or unknown user populations, mandatory for Enterprise.
• Server + CAL: cheaper below roughly 30 users, Standard only, still bound by the 24-core ceiling.
• Cores are licensed in 2-core packs with a four-core minimum per physical server — a 6-core server still costs four cores' worth if you configured it oddly.

Developer, Express and Web — the editions people forget to check first

SQL Server Developer edition is functionally identical to Enterprise and free, but licensed strictly for development and test. Using it for anything a production user touches — including a UAT environment real users validate against — is a licensing breach that shows up in audits.

Express is free and capped at 10 GB per database, 1 GB of memory and four cores; it is genuinely fine for small embedded workloads. Web edition is available only through hosting providers under SPLA. If your workload fits Express, neither Standard nor Enterprise is the conversation.

Frequently asked questions

Sources

• Microsoft — Editions and supported features of SQL Server 2022
• Microsoft — Compute capacity limits by edition
• Microsoft — SQL Server 2022 licensing datasheet
• Microsoft — Always On availability groups prerequisites