SQL Server Editions Compared

Standard and Enterprise are production editions. Express is free and has lower compute, memory, and database size limits. Developer is for development and testing, and SQL Server 2025 offers separate Developer editions for Standard and Enterprise features.

Enterprise vs. Standard vs. Express vs. Developer

EditionUseCheck before choosing
EnterpriseProduction with Enterprise scale or featuresFull Always On availability groups and online index create and rebuild
StandardProduction within Standard limitsSQL Server Agent and Basic Availability Groups. A Basic AG supports one database and two replicas.
ExpressSmall workloads and learningLower resource limits and no SQL Server Agent. Scheduled work needs an external scheduler.
Enterprise DeveloperDevelopment and testing with Enterprise featuresSQL Server 2022 calls its Enterprise-featured development edition Developer.
Standard DeveloperDevelopment and testing with Standard featuresAvailable in SQL Server 2025. Use it to test against the production edition’s feature set.
EvaluationEnterprise evaluationThe deployment expires after 180 days.

Express LocalDB is a lightweight, user-mode option for local development. For Web Edition, see the SQL Server 2022 matrix. For a production deployment, check the use rights in the Microsoft license terms and your agreement.

SQL Server 2025 and 2022 Standard and Express limits

LimitSQL Server 2025SQL Server 2022
Standard compute per instanceLesser of 4 sockets or 32 coresLesser of 4 sockets or 24 cores
Standard buffer pool per instance256 GB128 GB
Express relational database size50 GB per database10 GB per database
Express compute per instanceLesser of 1 socket or 4 coresLesser of 1 socket or 4 cores

A 20 GB database fits within the SQL Server 2025 Express size limit. Check compute, memory and scheduling requirements too. The same database exceeds the 10 GB limit of SQL Server 2022 Express. The buffer pool figures apply to that part of SQL Server memory. Analysis Services has its own limits.

Check the installed SQL Server edition before a move

SELECT SERVERPROPERTY('Edition') AS edition,
       SERVERPROPERTY('ProductVersion') AS engine_build;

Run the following in each application database and check reported features against the destination edition. Review instance-level dependencies separately, including SQL Server Agent jobs, availability groups, replication, and certificates used to restore encrypted backups.

SELECT feature_name
FROM sys.dm_db_persisted_sku_features;

Microsoft’s upgrade matrix lists which edition changes Setup can perform in place. For other paths, check whether a side-by-side migration is supported and test the database restores and instance dependencies on the new edition.

Supported SQL Server 2025 edition changesMicrosoft’s database feature checkIdentify the exact buildPlan the upgradeCompare failover options