SQL Server Web vs Standard: Web Edition Ends at SQL Server 2022

Fix it now

Microsoft states that SQL Server Web edition is not available for SQL Server 2025, and Learn confirms it is absent from 2025 and later versions. Where it does still exist, on SQL Server 2022 and earlier, it is offered only to hosters through the Services Provider License Agreement and only for publicly accessible web workloads.

1. Buy SQL Server 2025 Standard if you are an end customer licensing a database for your own use. Web was never sold to you and no longer exists in the current release.
2. Check your provider’s release if a hosting plan quotes Web edition. It has to be SQL Server 2022 or earlier, which reaches end of mainstream support on 12 January 2028.
3. Plan the move to Standard now if a hosted site runs on Web. There is no Web edition to upgrade into on SQL Server 2025.
4. Choose Standard whenever a database serves internal staff or reporting as well as a public site. Mixed use was always outside Web’s terms.
5. Use SQL Server Developer edition, not Web, for development and test. It is free and carries the Enterprise feature set, provided it never runs a production workload.
6. Do not assume Web is simply a cheaper Standard. It sat below Standard on compute and memory and lacked the high-availability feature set.

Web edition licensing is per core only. There is no Server plus CAL option and no CALs exist for it.

If you are buying SQL Server for your own organisation, Standard is the answer and you can stop. Below are the published ceilings for the last release that had Web, the SPLA channel rule, and what changed in SQL Server 2025 Standard.

Why it happens

The single fact that settles most of these conversations is that Web edition has gone. Microsoft’s SQL Server licensing guidance states that SQL Server Web edition is not available for 2025, and the Learn documentation for SQL Server 2022 carries the same note from the other direction: Web edition is not available in SQL Server 2025 and later versions. It survives only on SQL Server 2022 and earlier, which run to 12 January 2028 for mainstream support and 12 January 2033 for extended support.

Even where it exists, most people asking about it were never able to buy it. Microsoft’s SQL Server licensing FAQ is explicit: the Web edition is offered only to hosters through the Services Provider License Agreement. SPLA is a monthly subscription agreement for service providers and independent software vendors who deliver software services to end users, signed on a three-year term – it is not a channel an ordinary business can transact in for its own workloads. If you are licensing SQL Server to run your own application, Web edition was never on the menu.

The permitted-use restriction is the second half of the story. Web edition exists to sit behind publicly accessible web pages, sites, applications and services, which is why hosting companies use it for shared plans and public web tiers. A database that also serves internal staff, internal reporting, or a line-of-business front end is outside those terms whatever the technical configuration looks like. Mixed use has always ruled Web edition out; it does not become permissible because the workload is small.

Full reference

The published ceilings, on the last release that had Web

What SQL Server 2025 Standard changed

If you last looked at these numbers on SQL Server 2022, two of them have moved and both moved in your favour. Standard’s maximum compute capacity went from the lesser of 4 sockets or 24 cores to the lesser of 4 sockets or 32 cores, and the buffer pool ceiling went from 128 GB to 256 GB. That matters when you are sizing a server: a 32-core Standard instance is now a supported configuration where it previously would have wasted eight cores, and 256 GB of buffer pool moves the point at which Enterprise becomes necessary for memory reasons alone.

SQL Server 2025 was released on 18 November 2025, with mainstream support to 7 January 2031 and extended support to 7 January 2036. The editions in the current release are Enterprise, Standard, Enterprise Developer, Standard Developer, Evaluation and Express. Web is not among them.

How Standard is actually counted

Standard uses the same core-based model as the rest of the family. Licence every physical core on the server, subject to a minimum of four core licences per physical processor, with SKUs sold in packs of two core licences each. Licensing an individual virtual machine instead means buying licences for the virtual cores assigned to it, with a minimum of four per virtual operating system environment – and that model requires Software Assurance or subscription licences. Hyper-threading does not change the count when licensing physical cores; when licensing virtually, a virtual core maps to a hardware thread.

Standard also keeps the Server plus CAL model, which Enterprise no longer offers for new purchases. Existing Enterprise Server plus CAL licences with Software Assurance can be upgraded to current versions under that model, but they are restricted to server deployments of twenty cores or fewer. For an internal line-of-business application with a small, countable user population, Server plus CAL on Standard is frequently the cheaper of the two Standard routes – and it is the model that does not exist at all on Web.

The free options, checked honestly

Two SQL Server editions cost nothing and are frequently the correct answer. SQL Server Express is free and supported for production use, limited to the lesser of one socket or four cores and a small buffer pool, with its ceilings published on the editions page for the release you are installing. SQL Server 2025 also includes all the Advanced Services features in Express. If the database behind a public site is small and read-mostly, Express is a legitimate production choice and costs nothing at all.

SQL Server Developer edition – shipped in SQL Server 2025 as Enterprise Developer and Standard Developer – is licensed for use as a development and test system rather than a production server. Where a team asks for Web edition because it is cheap and the workload is a staging site, Developer is the correct and free answer, provided nothing production ever touches it.

If you are the hoster

For a service provider, the position is the reverse: SPLA is your channel, Web edition was designed for exactly your use case on releases up to 2022, and the question is what you move customers to. There is no Web edition in SQL Server 2025, so the plan tiers built on it need repricing against Standard, and the permitted-use restriction that made Web attractive – publicly accessible web workloads only – stops being a constraint at the same time. Check the SPLA product availability documents for the release you intend to offer rather than assuming the previous tier structure survives.

Questions people ask about this