SQL Server Standard vs Enterprise: Feature Comparison

Our SQL Server support team gets one sizing question more than any other: whether a workload needs Enterprise, or whether Standard — or even free Express — is enough. The answer is in the edition limits and the feature matrix, both published by Microsoft. This article covers the SQL Server 2022 numbers, with the 2025 changes noted where they differ.

Scale limits: Express vs Standard vs Enterprise

The hard limits per edition of SQL Server 2022, from Microsoft's editions and supported features page:

Two clarifications. First, the 10 GB Express cap is per database, not per instance — an Express instance can hold multiple databases of up to 10 GB each. Second, the core limit constrains a single instance, not the server; SQL Server ignores cores beyond the cap even if the license and hardware provide them. Details are on the compute capacity limits page.

High availability: the real dividing line

For most buyers, HA is what decides the edition, not raw limits.

Basic availability groups on Standard replace deprecated database mirroring: one database per group, one secondary, no read access on the secondary, no backups from the secondary. A server with ten databases needs ten separate basic AGs, each failing over independently — databases that must fail over together (an application with cross-database dependencies, for example) need Enterprise's full Always On availability groups. A two-node failover cluster instance (shared storage, whole-instance failover) is the other Standard-edition HA path and often the simpler one.

Performance features

Since SQL Server 2016 SP1, most programmability-surface features run in every edition, subject to the memory caps above. In 2022, all editions include: columnstore indexes, In-Memory OLTP, table and index partitioning, data compression, Query Store, temporal tables, Always Encrypted, row-level security, and dynamic data masking.

What remains Enterprise-only in 2022:

• Intelligent query processing extras — automatic tuning, batch mode on rowstore, batch mode adaptive joins, memory grant feedback, degree-of-parallelism feedback, cardinality estimation feedback.
• Online operations — online index create/rebuild, resumable online index rebuilds, online schema change, online page and file restore.
• Resource governor and I/O resource governance.
• Partitioned table parallelism and parallel index maintenance.
• Query Store on secondary replicas.

Standard also runs some shared features at reduced parallelism: batch mode operations and columnstore index builds are limited to DOP 2 on Standard versus unrestricted on Enterprise. On large columnstore workloads this shows up as measurably slower index maintenance, not a missing feature.

Security features

Transparent data encryption (TDE) moved from Enterprise-only to Standard in SQL Server 2019, and remains in Standard for 2022 — this removes what used to be the most common compliance-driven reason to buy Enterprise. Per the 2022 security feature table: Always Encrypted (including secure enclaves), row-level security, dynamic data masking, ledger tables, and server/database audit are in every edition including Express. TDE, backup encryption, and extensible key management (EKM) require Standard or Enterprise — Express and Web do not get them.

Price difference

Microsoft list prices for SQL Server 2022 (open no-level, per 2-core pack; cores are sold in packs of two with a 4-core minimum per server):

Enterprise costs roughly 3.8x Standard per core. On a 16-core server that is a difference of about $89,000 in list-price licensing. The gap is why edition selection is worth an assessment rather than a default; the mechanics of core counting, CALs, virtualization rights, and Software Assurance are covered in our SQL Server licensing guide, and download and install steps for each edition are in the SQL Server download guide.

Which edition for which workload

Express limitations in production

Express is a licensed, supported production edition — Microsoft places no non-production restriction on it (that restriction applies to Developer edition). Its practical constraints:

• 10 GB per database (50 GB in 2025). Inserts fail once the cap is hit; growth trend matters more than current size.
• 1,410 MB buffer pool. Anything beyond a small working set reads from disk; this, not CPU, is usually the first symptom.
• 4 cores / 1 socket. Concurrency ceilings appear well before the database size cap on busy systems.
• No SQL Server Agent. Scheduled backups and index maintenance need Task Scheduler plus sqlcmd or an external scheduler.
• No TDE, no backup compression, no log shipping — no built-in HA or encryption-at-rest path.

Express is a reasonable production choice for small, slow-growing databases where a nightly backup is acceptable recovery: a point-of-sale terminal, a small internal tool, an application vendor's embedded database. It is the wrong choice the moment the business depends on the data being available within minutes of a failure.

FAQ

Is SQL Server Standard good enough for production?

For most workloads, yes. Since TDE arrived in Standard (2019) and columnstore, In-Memory OLTP, and partitioning arrived earlier (2016 SP1), the Enterprise case narrowed to multi-database availability groups, readable secondaries, online index operations, resource governance, and instances that need more than 128 GB of buffer pool or 24 cores.

Can I upgrade from Express to Standard without reinstalling?

Yes. SQL Server setup supports edition upgrade in place (Maintenance → Edition Upgrade) with a new product key; databases and configuration carry over. Supported paths are listed in Microsoft's supported version and edition upgrades documentation.

Does SQL Server Standard support Always On?

Partially. Standard supports Always On failover cluster instances (2 nodes) and basic availability groups (one database, one non-readable secondary per group). Full Always On availability groups — multiple databases per group, up to 8 secondaries, readable secondaries — require Enterprise.