About this article: AI-assisted writing, reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
A business application vendor may state a minimum SQL Server edition. When an application moves to a hosted virtual machine, the edition question comes back: is Express enough, does Standard limit the server, and when is Enterprise actually needed?
This article sets out the limits Microsoft publishes for each edition, which of them tend to matter for a business application, and what changed in SQL Server 2025. It covers SQL Server installed on a VM, not Azure's platform database services, and it does not cover licensing prices or terms.
Why it matters
Edition limits are enforced by the software. An instance that reaches its edition's processor or memory limit simply does not use more, however large the VM is. Paying for a bigger VM without checking the edition can buy capacity SQL Server will not use.
Features matter as well. Some maintenance, availability and security features exist only in certain editions. Discovering that after a migration is expensive.
How it works
The editions
Microsoft's SQL Server 2025 page lists Enterprise, Standard, Express, two Developer editions and Evaluation. The Developer editions include the features of Enterprise or Standard but are licensed for use as a development and test system, not as a production server. Evaluation includes Enterprise features for 180 days.
Web edition, offered to hosting providers in earlier versions, is gone: Web edition isn't available in SQL Server 2025 (17.x) and later versions. A hosted application on Web edition needs a different edition when it moves to SQL Server 2025.
Scale limits
The limits below are per instance of the Database Engine, from Microsoft's edition pages.
| Limit | Enterprise (core-based licensing) | Standard 2025 | Standard 2022 | Express 2025 | Express 2022 |
|---|---|---|---|---|---|
| Processors | Operating system maximum | Lesser of 4 sockets or 32 cores | Lesser of 4 sockets or 24 cores | Lesser of 1 socket or 4 cores | Lesser of 1 socket or 4 cores |
| Buffer pool memory | Operating system maximum | 256 GB | 128 GB | 1,410 MB | 1,410 MB |
| Database size | 524 PB | 524 PB | 524 PB | 50 GB | 10 GB |
The Enterprise processor entry above applies to core-based licensing. Microsoft's edition and compute-capacity pages give legacy Enterprise Server+CAL deployments a 20-core per-instance limit. Check migrated installations before assuming operating-system maximum capacity.
The buffer pool is the memory SQL Server uses to cache data. It is closely tied to performance, because data held in memory does not need to be read from disk.
How the processor limit applies on a VM
On a virtual machine, the limit counts something different from a physical server. Microsoft explains that In a virtualized environment, the compute capacity limit is based on the number of logical processors, not cores. In practice, this means each virtual CPU the guest sees counts toward the edition limit.
So a Standard 2022 instance on a VM with 32 virtual CPUs uses at most 24 of them. An Express instance on an 8-vCPU VM uses at most four. These limits apply per instance, not to the VM as a whole.
Feature differences that can affect business applications
Microsoft's feature tables list many differences. This selection can affect a hosted business application:
| Feature | Enterprise | Standard | Express |
|---|---|---|---|
| SQL Server Agent (scheduled jobs) | Yes | Yes | No |
| Backup compression | Yes | Yes | No |
| Online index create and rebuild | Yes | No | No |
| Always On availability groups | Yes | Basic only: two replicas, one database | No |
| Failover cluster instances | Yes, up to 16 nodes | Yes, two nodes | No |
| Transparent data encryption | Yes | Yes | No |
| Resource Governor | Yes | Yes in 2025; no in 2022 | No |
The table summarises the SQL Server 2025 and 2022 pages; check the page for your version before deciding.
Two notes on Express. Without SQL Server Agent, scheduled backups and maintenance need another scheduler, such as Windows Task Scheduler. Starting with SQL Server 2025, Express edition includes all the functionality that was available in SQL Server Express edition with Advanced Services.
One note on Standard. Without online index rebuilds, rebuilding a large index can block users of that table while it runs, so index maintenance needs a quiet window.
What to choose and why
Express
Express can suit a small application with a database that will stay well under the size limit and that works within 1,410 MB of buffer pool. Plan backups without SQL Server Agent. Check the application vendor supports Express for production use.
Standard
Standard is the next step for a business application that outgrows Express. Check two things before sizing the VM: that the virtual CPUs you buy do not exceed the edition's processor limit for your version, and that the buffer pool limit is above what the database needs to keep in memory. Basic availability groups and two-node failover clusters give some high availability; their limits are covered in a separate article.
Enterprise
Enterprise is justified by a specific need: more processors or memory than Standard allows, online index operations on large tables that cannot have a maintenance window, or full availability groups with readable secondaries. Name the need before paying for it.
When upgrading versions
Moving from SQL Server 2022 to 2025 raises the Standard limits and the Express database size limit, and adds Resource Governor to Standard. Moving off Web edition requires choosing another edition.
Risks and limits
- This article does not cover licensing. Edition limits are technical; licensing terms, prices and core minimums are separate and are set by Microsoft's licensing documents.
- Vendor requirements come first. An application vendor may require a specific edition or version for support.
- Several instances add up. Limits apply per instance, but each instance still needs memory and processors from the same VM.
- Feature tables change. Microsoft updates these pages; check the current version before a decision.
- Test on an isolated copy. Before moving production to a different edition, restore a copy of the database with synthetic or masked data to a test VM running the target edition, and run the application's normal and month-end workload against it.
Sources
Opened 14 November 2026.
- Microsoft Learn: Editions and supported features of SQL Server 2025.
- Microsoft Learn: Editions and supported features of SQL Server 2022.
- Microsoft Learn: Compute capacity limits by edition of SQL Server.
Related service: Cloud hosting.
Related future topics
- High availability on SQL Server Standard edition.
- SQL Server licensing in virtual machines.
- SQL Server memory on a hosted VM.
Learning notes
- On a VM, each virtual CPU counts toward the edition's processor limit.
- Standard 2025 allows up to 32 cores and 256 GB of buffer pool; Standard 2022 allows 24 cores and 128 GB.
- Express is limited to four cores, 1,410 MB of buffer pool and a 50 GB database in 2025 (10 GB in 2022), and has no SQL Server Agent.
- Web edition is not available from SQL Server 2025.
- Choose Enterprise for a named need, not by default.
This article was originally published on .