Which SQL Server Edition Do You Need?

Which SQL Server edition you need is a question with a free answer more often than people expect. Two of the four editions cost nothing, and one of those two is the full product with every feature switched on. The catch is what you are allowed to do with it, and that catch turns up in audits.

Start by Finding Out What You Have

Before choosing, check what is already installed. People are wrong about this surprisingly often.

SELECT SERVERPROPERTY('Edition')       AS Edition,
       SERVERPROPERTY('EngineEdition') AS EngineEdition;

Edition                                EngineEdition
Enterprise Developer Edition (64-bit)  3

That is my own machine. Note what it says. Developer Edition reports itself as Enterprise, because that is exactly what it is. The word Developer is the licence, not the capability.

The Four Editions

Express is free and may be used in production. It is limited on purpose: a small cap on database size, a small cap on memory, and only a handful of cores. It also has no SQL Server Agent, which surprises people more than the size limit. No Agent means no scheduled jobs and no scheduled backups without writing your own scheduling.

Developer is free and is the complete Enterprise product with nothing removed. Every feature, no limits. You may use it for development and testing only. Not for production, not for a system real people rely on, not for a reporting server the business depends on.

Standard is the normal paid edition and the right answer for most businesses. It caps memory and cores well above anything Express allows, and it covers the features most systems actually use.

Enterprise removes the caps and adds the features built for large or demanding systems. It costs considerably more, and it is worth it when you need what it has.

Exact limits move between releases, so check the current documentation for your version rather than trusting a number in a blog post, including this one.

The Trap

Here is the one that costs money. Somebody installs Developer Edition because it is free and complete, builds something on it, and it quietly becomes important. A year later it is running the business.

Nothing warns you. The software does not stop, there is no nag screen, and the server runs beautifully, because it is Enterprise. The problem only appears when somebody counts licences, and by then you are not choosing an edition, you are buying one under pressure.

This is why I run the edition query across every instance during a health check. Finding a Developer Edition instance with real users on it is common, and it is always a surprise to somebody.

Choosing

The decision is usually short.

Learning, a sandbox, a test rig or writing code: Developer Edition. It is free and it behaves exactly like the expensive one, which means your tests are meaningful.

A genuinely small production system, such as a single application with a modest database and no scheduled work: Express can be the right call. Plan for what happens when it outgrows the limits, because that day arrives without notice.

A real production system: Standard, unless you can name the specific Enterprise feature you need. Naming it is the test. If nobody can say which feature justifies the price, the answer is Standard.

What About Azure

Azure SQL Database does not have editions in this sense. You choose a service tier and a size instead, and you can change it later without reinstalling anything. The EngineEdition value in the query above returns 5 there, which is a quick way for a script to tell where it is running.

If you are weighing Azure against a machine you own, the honest comparison is not a feature list. It is who patches it, who watches the backups, and who gets the call at night.

Upgrading Later

Moving up an edition is easier than people fear. Setup has an edition upgrade path that keeps your databases in place, and moving from Developer to Standard or Enterprise does not need a rebuild.

Moving down is the hard direction. Going from Enterprise to Standard can fail outright if the databases use features Standard does not have. Check for those features before planning that move, not during the outage window.

Developer Edition is not a cheap Enterprise, it is Enterprise with a promise attached.

This post was rewritten from scratch in September 2026. The original, published on 2014-05-04, was a short announcement about something that no longer exists. The address is the same, the subject is now a basic idea worth keeping.

Published by Pinal Dave on SQLAuthority. More of my work at pinaldave.com.