Quick answer: SQL Server 2025 Express is free but capped at 4 cores, about 1.4 GB of buffer pool memory and 50 GB per database. Standard raises that to 32 cores and 256 GB, adds SQL Agent, basic availability groups, backup compression and now Resource Governor. Enterprise removes the limits and adds full Always On, online operations and advanced performance features.
Written by the Softkeyworld technical team · Updated October 2026
Choosing a SQL Server edition used to be fairly simple: Express for tiny apps, Standard for most businesses, Enterprise for anything mission-critical. SQL Server 2025, which reached general availability on 18 November 2025, shifts the boundaries. Standard got its biggest capacity increase in years, Express became more useful, and Microsoft retired the Web edition and Express with Advanced Services altogether.
This guide compares the three editions most organisations actually choose between, using the limits in Microsoft's editions and supported features of SQL Server 2025 page. It's about choosing the right edition; if you already have a key and need the setup steps, our SQL Server 2025 Standard installation guide covers that.
Key takeaways
- Standard 2025 supports up to 4 sockets or 32 cores and 256 GB of buffer pool memory, up from 24 cores and 128 GB in SQL Server 2022.
- Express 2025 raises the database size cap from 10 GB to 50 GB but still has no SQL Server Agent.
- Resource Governor, previously Enterprise-only, is now included in Standard.
- Mainstream support runs to 7 January 2031 and extended support to 7 January 2036.
SQL Server 2025 editions at a glance
| Limit or feature | Express | Standard | Enterprise |
|---|---|---|---|
| Compute per instance | Lesser of 1 socket or 4 cores | Lesser of 4 sockets or 32 cores | Operating system maximum |
| Buffer pool memory | 1,410 MB | 256 GB | Operating system maximum |
| Columnstore segment cache / memory-optimised data | 352 MB each | 32 GB each | Unlimited |
| Maximum database size | 50 GB | 524 PB | 524 PB |
| SQL Server Agent (scheduled jobs) | No | Yes | Yes |
| High availability | None (no log shipping, no clustering) | Basic AGs (2 replicas, 1 database each), 2-node failover cluster, log shipping | Full Always On AGs, readable secondaries, up to 16-node clusters |
| Transparent Data Encryption | No | Yes | Yes |
| Resource Governor | No | Yes (new in 2025) | Yes |
| Online index rebuilds, resumable operations | No | No | Yes |
| Backup compression | No | Yes | Yes |
| Licensing | Free | Per core, or Server + CAL | Per core only |
Features such as columnstore indexes, In-Memory OLTP, table partitioning, data compression and Always Encrypted are available in all three editions; the differences are in how much memory those features may use, not whether they exist.
What changed in SQL Server 2025 editions
If you last chose an edition for SQL Server 2019 or 2022, these are the changes that affect the decision, as listed in Microsoft's What's new in SQL Server 2025:
- Standard capacity increased to 32 cores and 256 GB of buffer pool memory. Many workloads that previously forced an Enterprise purchase purely for memory now fit in Standard.
- Resource Governor in Standard. You can now cap CPU, memory and I/O for reporting users or ETL jobs so they don't starve your line-of-business app.
- Express database cap raised to 50 GB, and Express now includes the features that used to need the separate "Express with Advanced Services" download.
- Web edition discontinued. Hosting providers who used it need to move to Standard or a different licensing route.
- Two free developer editions: Enterprise Developer and the new Standard Developer, which lets you test against exactly the feature set you'll deploy.
- Reporting consolidated under Power BI Report Server rather than a separate SQL Server Reporting Services release.
The headline engine features, including the native vector data type, REGEXP_LIKE and the other regular-expression functions, the native JSON type, optimised locking and ZSTD backup compression, are part of the core engine rather than edition-gated, although some (such as vector indexes) were still flagged as preview features at launch.
SQL Server 2025 Express: when free is enough
Express is a production-capable edition, not a trial. It's the right choice for:
- Desktop or small client-server applications shipped by software vendors (practice management, EPOS back offices, small CRMs).
- Departmental databases that stay comfortably under 50 GB per database.
- Learning, prototypes and lightweight web back ends.
The limits that bite in practice are not usually the 50 GB cap. They're the 1,410 MB buffer pool, which means a database larger than about 1.5 GB starts reading from disk constantly as it grows, and the missing SQL Server Agent. Without Agent you have to schedule backups and index maintenance with Windows Task Scheduler and sqlcmd scripts. That works, but it's easy to forget, and a common story in small offices is an Express database with no working backup for months.
Note that each database can be 50 GB, but all databases on one instance share the same 4-core and 1,410 MB memory ceiling.
SQL Server 2025 Standard: the default for most businesses
Standard is the edition we recommend for most small and mid-sized organisations running ERP, accounting, CRM or line-of-business systems. You move to Standard when you need any of these:
- More than 4 cores or more than about 1.4 GB of cache. Most ERP systems with more than a handful of users will need this.
- SQL Server Agent for backups, maintenance plans and scheduled imports.
- Some high availability: a two-node failover cluster, log shipping to a standby server, or basic availability groups that protect one database per group with a single secondary replica (which can't be read from).
- Encryption at rest through TDE, which is often a compliance requirement for personal data.
- Workload control with Resource Governor.
The things Standard still does not offer are online index rebuilds (index maintenance on Standard takes locks that can block users, so schedule it out of hours), readable secondary replicas, multi-database availability groups and memory beyond 256 GB.
SQL Server 2025 Enterprise: when you genuinely need it
Enterprise is justified when downtime or scale is the main risk rather than cost:
- 24/7 systems that cannot accept blocking during index maintenance or schema changes.
- Availability groups with multiple databases failing over together, multiple secondaries, or readable secondaries for reporting.
- Servers with more than 32 cores or workloads that need more than 256 GB of cache.
- Heavily virtualised estates, where Enterprise per-core licensing with Software Assurance allows unlimited virtualisation.
- Advanced performance features such as batch mode on rowstore and automatic tuning.
One technical note we see trip people up: Enterprise edition isn't supported on Windows 10 or Windows 11. It needs Windows Server 2019, 2022 or 2025. Standard and Express can run on client Windows, which is handy for small offices and test machines.
Licensing models explained
Standard offers two ways to licence a server:
- Server + CAL: licence the server, then buy a SQL Server Client Access Licence for every user or device that accesses it. This is usually best when you have a small, known number of internal users.
- Per core: licence every physical core (minimum four per processor or virtual machine) and allow unlimited users. This suits public-facing websites or large user counts where counting CALs is impractical.
Two points that cause most licensing mistakes. First, SQL Server CALs are separate from Windows Server CALs; users of a SQL database on Windows Server typically need both. Our guide to Windows Server CALs, user vs device explains the Windows side. Second, multiplexing doesn't reduce CAL counts: if 40 staff reach the database through a web app or middleware, you count the 40 people, not the one service account.
Requirements and support dates
| Item | SQL Server 2025 |
|---|---|
| Supported Windows | Windows Server 2019, 2022, 2025; Windows 10 and 11 (not Enterprise edition) |
| Processor | x64, 1.4 GHz minimum, 2.0 GHz or faster recommended |
| Memory | 512 MB minimum for Express; 1 GB minimum (4 GB+ recommended) for other editions |
| Disk | 6 GB free minimum |
| Mainstream support ends | 7 January 2031 |
| Extended support ends | 7 January 2036 |
The dates come from the SQL Server 2025 lifecycle page. If you're building a new database server, pairing SQL Server 2025 with Windows Server 2025 Standard gives you the longest combined support runway; we compare that release with its predecessor in Windows Server 2025 vs 2022.
Common scenarios and the edition that fits
These are the situations we're asked about most often, with the edition we'd normally point people towards.
A 10-person firm running accounting or practice software
If the vendor supports Express and the database is a few gigabytes, Express can work, but add scripted backups on day one. Once the database passes roughly 5–10 GB, or users complain about slow month-end reports, Standard with Server + CAL licensing is usually the better long-term choice.
An ERP system with 30 to 150 users
Standard is the norm here. Give the server enough RAM to cache the hot data (64–128 GB is common), use Agent for nightly maintenance and log backups every 15 minutes, and consider log shipping or a basic availability group to a second server for disaster recovery.
An ecommerce or public web application
With anonymous internet users you can't count CALs, so you need per-core licensing. With Web edition gone, that means Standard per core for most sites, or Enterprise per core if you need readable secondaries to scale out reads.
Upgrading from SQL Server 2016 or 2017
Re-check your edition rather than renewing like for like. Some servers that needed Enterprise in 2016 purely for memory now fit within the Standard 2025 limits. Test application compatibility first, because database compatibility levels and query optimiser changes can affect older code.
How to decide: a quick checklist
- Check your largest database and expected growth over five years. Over 50 GB rules out Express.
- Look at memory use. If your working set is well over 1.5 GB, Express will be slow.
- Ask whether you need scheduled jobs. If yes, you want Standard or above.
- Define your recovery time objective. Minutes with manual failover suits Standard; seconds with automatic multi-database failover points to Enterprise.
- Check what your application vendor certifies. Many ERP vendors specify a minimum edition.
- Count users and devices to choose between Server + CAL and per-core licensing.
A practical pattern: develop on Standard Developer (free), run small satellite sites on Express, and run the main production database on Standard. You can upgrade an Express instance in place to Standard later through SQL Server Installation Center > Maintenance > Edition Upgrade by entering a Standard key, with no reinstall or data migration.
Frequently asked questions
Is SQL Server 2025 Express free for commercial use?
Yes. Express is free to use in production, including commercially, within its limits of 4 cores, 1,410 MB of buffer pool memory and 50 GB per database.
What is the maximum database size in SQL Server 2025 Express?
50 GB per database, up from 10 GB in earlier versions. The limit applies to data files; log files don't count towards it.
How much memory can SQL Server 2025 Standard use?
Up to 256 GB for the buffer pool per instance, plus separate allowances for columnstore and memory-optimised data. The server can have more RAM; SQL Server simply won't use more than the cap for the buffer pool.
Can I upgrade from Express to Standard without reinstalling?
Yes. Run SQL Server setup, choose Maintenance > Edition Upgrade, enter your Standard product key and select the instance. Databases and settings are kept.
Does SQL Server 2025 still have a Web edition?
No. Microsoft discontinued Web edition with SQL Server 2025, along with the separate Express with Advanced Services package.
Do I need Windows Server CALs as well as SQL Server CALs?
Usually yes. Users accessing SQL Server on Windows Server are using both products, so each needs its own access licensing unless SQL Server is licensed per core.
Our recommendation
For most businesses, SQL Server 2025 Standard is the sweet spot: the 2025 increases to 32 cores and 256 GB, plus Resource Governor, close much of the gap that once pushed small firms towards Enterprise. Start with Express only if your data and user count are genuinely small, and reserve Enterprise for systems where online maintenance and multi-replica availability are essential. Our SQL Server 2025 Standard licence is available with User CAL or Device CAL options.
Related reading
| Resource | Why read it |
|---|---|
| SQL Server 2025 Standard installation guide | Step-by-step download, setup and activation once you've chosen Standard |
| Windows Server CALs explained | Work out the Windows Server access licences your SQL users also need |
| Windows Server 2025 vs 2022 | Pick the right operating system for a new database server |