Which SQL Server 2025 edition do you need? For small applications with databases up to 50 GB, the free Express is often enough. As soon as you need scheduled backups with SQL Server Agent, more than 4 cores, more memory or larger databases, Standard is the usual choice.
Enterprise pays off for very high load, more than 32 cores and demanding high availability. The tables below show the differences according to Microsoft’s information for SQL Server 2025 (version 17.x).
Quick decision
Express is enough if …
- your database stays below 50 GB and will for the foreseeable future,
- 4 cores and about 1.4 GB of buffer pool memory are sufficient (small line-of-business application, few concurrent users, development, learning),
- you can do without SQL Server Agent. You then schedule backups, for example, with Windows Task Scheduler and
sqlcmd.
Standard is right if …
- the database grows beyond 50 GB or the application should use more cores and memory (up to 32 cores and 256 GB of buffer pool memory per instance),
- you want to control scheduled jobs, backups and maintenance with SQL Server Agent,
- you need to compress and encrypt backups or encrypt the database with TDE,
- you use log shipping, a basic availability group or a two-node failover cluster,
- your software vendor requires Standard, for example for inventory management, ERP or practice software with several workstations.
You need Enterprise if …
- one instance should use more than 32 cores or more than 256 GB of buffer pool memory,
- you run Always On availability groups with several readable replicas or clusters with more than two nodes,
- indexes must be rebuilt online and maintenance done while the system is running,
- you want to use the advanced query processing performance features (batch mode on rowstore, automatic tuning).
Whether your application is certified for a specific edition is stated in your software vendor’s system requirements. If in doubt, ask them before you buy licenses.
Performance and capacity limits
| Feature | Express | Standard | Enterprise |
|---|---|---|---|
| Compute capacity per instance | 1 socket or 4 cores (whichever is lower) | 4 sockets or 32 cores (whichever is lower) | operating system maximum |
| Memory for the buffer pool per instance | 1,410 MB | 256 GB | operating system maximum |
| Columnstore segment cache per instance | 352 MB | 32 GB | unlimited |
| Memory-optimized data per database | 352 MB | 32 GB | unlimited |
| Maximum database size | 50 GB | 524 PB | 524 PB |
| Instances per computer | 50 | 50 | 50 |
The limits apply per SQL Server instance and concern the memory areas named, not the total memory of the SQL Server process. Compared with SQL Server 2022, Microsoft has raised the limits: Standard 2022 was limited to 24 cores and 128 GB of buffer pool, Express 2022 to 10 GB per database.
Database features and performance
| Feature | Express | Standard | Enterprise |
|---|---|---|---|
| SQL Server Agent (scheduled jobs) | No | Yes | Yes |
| Columnstore indexes | Yes | Yes | Yes |
| In-Memory OLTP | Yes (up to 352 MB) | Yes (up to 32 GB) | Yes |
| Table and index partitioning | Yes | Yes | Yes |
| Data compression | Yes | Yes | Yes |
| Resource Governor | No | Yes | Yes |
| Partitioned table parallelism | No | Yes | Yes |
| Optimized locking | No | Yes | Yes |
| Automatic tuning | No | No | Yes |
| Batch mode on rowstore | No | No | Yes |
| Batch mode adaptive joins | No | No | Yes |
| Online index create and rebuild | No | No | Yes |
Batch mode operations run with at most 2 parallel threads in Standard and with one in Express. Express LocalDB does not include In-Memory OLTP.
High availability, backup and security
| Feature | Express | Standard | Enterprise |
|---|---|---|---|
| Database backup and snapshot backup | Yes | Yes | Yes |
| Backup compression | No | Yes | Yes |
| Encrypted backups | No | Yes | Yes |
| Transparent Data Encryption (TDE) | No | Yes | Yes |
| Always Encrypted, row-level security, dynamic data masking | Yes | Yes | Yes |
| Log shipping | No | Yes | Yes |
| Basic availability groups (2 replicas, 1 database) | No | Yes | – (full availability groups) |
| Always On availability groups | No | No | Yes (up to 8 secondary replicas) |
| Failover cluster instances | No | 2 nodes | up to 16 nodes |
| Accelerated database recovery | No | Yes | Yes |
| Online page and file restore | No | No | Yes |
| Change data capture | No | Yes | Yes |
Programmability, AI and management
| Feature | Express | Standard | Enterprise |
|---|---|---|---|
| SQL Server Management Studio (free download) | Yes | Yes | Yes |
| Full-text search | Yes | Yes | Yes |
| Native JSON data type, XML | Yes | Yes | Yes |
| Vector data type and embedding functions | Yes | Yes | Yes |
| Vector index (DiskANN) | Yes (preview) | Yes (preview) | Yes (preview) |
| Query Store | Yes | Yes | Yes |
| Linked servers | Yes | Yes | Yes |
| Database Mail | No | Yes | Yes |
| Service Broker | client only | Yes | Yes |
| SQL Profiler | No | Yes | Yes |
| Python and R integration | basic | basic | advanced (all cores) |
| Transactional replication | subscriber only | Yes | Yes |
| Peer-to-peer replication | No | No | Yes |
You enable preview features per database with the PREVIEW_FEATURES setting; they are not yet supported for production use. Since SQL Server 2025, Express includes the features of the former “Express with Advanced Services”, among them full-text search.
Licensing models: server + CAL or per core
| Feature | Express | Standard | Enterprise |
|---|---|---|---|
| Cost | free | paid | paid |
| Production use | Yes | Yes | Yes |
| Server + CAL | – | Yes | No |
| Per core | – | Yes | Yes |
Server + CAL is available for Standard only. You license each server with a server license and additionally need a client access license (CAL) for every user or device that accesses SQL Server:
- A user CAL covers one person, regardless of the device used. Useful when staff work with a laptop, PC and smartphone.
- A device CAL covers one device, regardless of who uses it. Useful for shift work or shared checkout and warehouse computers.
- Indirect access needs a CAL too: if 20 employees access the database through a web application or an application server, you need 20 CALs, not one.
- A CAL entitles access to SQL Server of the same or an earlier version. For SQL Server 2025 you therefore need version 2025 CALs.
- Per server license you may run one SQL Server instance in a physical or virtual environment.
Per core you license the server’s processor cores (at least 4 core licenses per processor; sold in 2-core packs). No CALs are needed then, and any number of users and devices may access the server. This model fits when you cannot count the users, for example for public web applications, or when very many users access a small server. For new agreements, Enterprise is available per core only.
Rule of thumb: with few, easily countable users, server + CAL is often cheaper; with many or an unknown number of users, the per-core model. Rights for passive failover servers (high availability, disaster recovery) and licensing individual virtual machines require Software Assurance or a subscription, according to Microsoft.
Besides Express, the Enterprise Developer and Standard Developer editions are also free: they include the full feature set of the respective edition but may only be used for development, testing and demonstration, not in production.
SQL Server at VivaKeys
Core licenses – licensed per core, without CALs for the users:
Client access licenses (CALs) for SQL Server 2025 Standard in the server + CAL model, i.e. in addition to a server license (with a core license you need no CALs):
Earlier versions, for example if your software vendor requires a specific version:
SQL Server 2022 Standard (16 or 24 cores),
SQL Server 2022 Enterprise and
SQL Server 2019 Standard (10 to 24 cores). Note the lower limits of these versions: Standard 2022 and 2019 use at most 24 cores per instance.
All offers with current prices are in the
SQL Server category. How many cores or CALs your environment needs, we are happy to clarify with you before you order – just tell us the number of users or devices, servers, processors and cores, and your software vendor’s requirements.
Frequently asked questions
May I use SQL Server Express in production in my company? Yes. Express is free and also licensed for production use. Only the Developer and Evaluation editions are limited to development, testing and evaluation.
What happens when my Express database reaches 50 GB? The limit applies per database. Once reached, the database cannot grow any further. You can upgrade Express to Standard or Enterprise without reinstalling the databases.
Do I need a server license and CALs for SQL Server 2025 Standard? In the server + CAL model, yes: one server license per server and one CAL per user or device. If you license per core instead, no CALs are needed.
Are my SQL Server 2022 CALs valid for SQL Server 2025? No. CALs entitle access to the same or earlier versions. For SQL Server 2025 you need version 2025 CALs; these in turn also cover earlier SQL Server versions.
Does SQL Server 2025 run on Windows 11? Express, Standard and the Developer editions do. Enterprise requires Windows Server (Windows Server 2019 or later). SQL Server 2025 also runs on Linux.
How long does SQL Server 2025 receive updates? According to Microsoft, mainstream support ends in January 2031 and extended support with security updates in January 2036.
Sources
Checked on 2026-11-09 against the publisher’s information:
- learn.microsoft.com/en-us/sql/sql-server/editions-and-components-of-sql-server-2025
- www.microsoft.com/licensing/guidance/SQL
- www.microsoft.com/licensing/terms/productoffering/SQLServer/MCA
- learn.microsoft.com/en-us/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2025
- learn.microsoft.com/en-us/sql/sql-server/editions-and-components-of-sql-server-2022
- learn.microsoft.com/en-us/lifecycle/products/sql-server-2025