Four editions, four very different bargains. The free one with every feature is not licensed for your live business, and the free one that is licensed for business stops at 10 GB. Here is each edition graded honestly.
People usually pick a SQL Server edition by whichever download button they see first. That is how offices end up running a live billing database on Developer edition — a licensing violation — or hitting the Express ceiling on the busiest day of the year. SQL Server 2022 comes in four main editions, and the right choice depends on one question: will real users depend on this database?
Developer edition contains the complete Enterprise feature set: no size cap worth worrying about, all the memory your machine has, partitioning, advanced security — everything. It costs nothing. The catch is purely legal, not technical: its licence covers development and testing only. Developers build against it because an app developed on Developer behaves exactly as it will on Enterprise. If you are learning SQL Server or following our installation guide on your own PC, this is the edition to install — it will never block a feature you are trying to learn.
Express is the only edition that is free and licensed for production, which makes it the honest default for a tiny application: a small shop's billing database, a single-user tool, a low-traffic website. Respect its three walls. Each database is limited to 10 GB — generous until years of data arrive. The buffer pool is capped at 1,410 MB of RAM and it uses at most four cores, so it will not speed up just because the server is powerful. And there is no SQL Server Agent, so scheduled backups and maintenance jobs must run through Windows Task Scheduler and scripts instead. None of this is hidden — Express is a fair deal as long as you read the label.
Standard is the edition most small and medium businesses should actually buy. It removes the Express ceilings that matter (databases up to 524,272 TB in theory, 128 GB buffer pool), includes SQL Server Agent for scheduled jobs and maintenance plans, and covers the features real production uses daily: backups with compression, basic high availability with two-node clustering and log shipping, and the common security features. Licensing is by core (with a minimum per server) or by server plus CALs — which model is cheaper depends on how many users connect, and it is worth one calculation before buying.
Enterprise removes the remaining limits: unlimited cores and memory, online index operations, advanced compression, Always On availability groups with multiple readable replicas, and the highest-end security and analytics features. It is licensed per core and priced accordingly. Honest grading: almost no small office needs Enterprise. You need it when downtime is measured in lakhs per minute, when databases are measured in terabytes, or when a specific Enterprise-only feature is on your requirements list — not because it is the 'best' one.
Here is the reassuring part: editions are not a life sentence. SQL Server supports edition upgrades in place — the setup's Edition Upgrade option moves Express to Standard, or Developer to Standard, keeping your instance, databases and settings. Data files do not care which edition reads them. So starting a small project on Express is safe engineering, not a trap, as long as you watch the 10 GB line before it watches you. The reverse direction (downgrading) is not supported, which is one more reason to test on Developer before buying.
Match the edition to the job, not to your ambition. Learning or developing: Developer. A small real application with modest data: Express, with a calendar reminder to check database size every few months. A business database people depend on: Standard. Very large or mission-critical systems: Enterprise, and you will already know why. When you are ready, our complete SQL Server 2022 setup guide walks the install itself screen by screen.
See the editions in the video's install walkthrough — where to download each one and which option to pick on the setup screen.
▶️ Watch Full VideoNew data stops being written and applications start throwing errors — the database does not gracefully spill over. Watch the size in SSMS, archive old data before you get close, and plan an edition upgrade to Standard, which is an in-place setup operation that keeps your databases and settings.
Yes, and that is exactly the intended workflow. A database backup taken on Developer restores cleanly on Standard or Enterprise, as long as you did not use Enterprise-only features in a way your target edition lacks. Test the restore on the real target before go-live day.
LocalDB is a tiny developer variant of the Express engine that starts on demand. The SQLEXPRESS name you see in old tutorials is simply the default name setup used to give an Express named instance — the instance name is your choice during install, not a different product.