SQL Server Web Edition Review: Discontinued for 2025, and What Replaces It

Fix it now

There is no SQL Server 2025 Web edition. Microsoft’s licensing guidance states that Web is not available for 2025 although SQL Server 2022 Web may still be available under SPLA, and Web is absent from the 2025 editions page entirely. If you came here to buy it, this article is about what to buy instead.

1. If you are an end customer, stop looking for Web. It was never sold to you, and for 2025 it is not sold at all. SQL Server 2025 Standard or Express is your answer.
2. If you are a hosting provider with public web workloads on Web edition, plan around SQL Server 2022 Web under your Services Provider Licence Agreement, and confirm availability with your SPLA reseller rather than assuming.
3. Price SQL Server 2025 Standard against staying on 2022 Web. Standard’s ceilings rose to 32 cores and 256 GB of buffer pool in this release, so the gap is wider than the old comparison suggested.
4. Skip any offer of SQL Server 2025 Web keys. The SKU does not exist, whatever the listing says.
5. Check what edition backs the database in a hosting plan before you sign it. It decides your ceilings and whether availability groups are available to you at all.
6. If the workload is small and public, SQL Server 2025 Express with its 50 GB per database may cover it without any licence at all.

SQL Server 2022 Web edition supports no availability groups and no failover cluster instances. Log shipping and subscriber-only replication are the resilience tools it has.

If you needed to know whether the SKU exists, you have your answer. The next section covers what Web edition was for, why its disappearance matters and what actually replaces it.

Why it happens

Web edition existed to give hosting providers a cheaper way to run customer websites. It was available under the Services Provider Licence Agreement, a monthly programme through which providers report and pay for what they used, and it was never sold in retail or volume licensing channels. There was no perpetual form and no route by which a company could buy it for hardware it owns and operates for itself.

That is now history rather than a restriction. Microsoft’s SQL Server licensing guidance states that SQL Server Web edition is not available for 2025, although SQL Server 2022 Web edition may be available. The SQL Server 2025 editions page confirms it from the other direction: it lists Enterprise, Standard, Enterprise Developer, Standard Developer, Evaluation and Express, and no Web. For anyone whose hosting business was built on Web edition pricing, that is a commercial event rather than a footnote.

The use restriction was always as important as the channel, and it still applies to the 2022 edition a provider may continue to run. The terms confined Web edition to supporting publicly accessible web pages, sites, applications and services. Running an internal line-of-business application on it, or serving your own staff, fell outside that. Providers deploying it need to be as careful about what the instance is used for as about counting cores.

On capability, SQL Server 2022 Web sits between Express and Standard, and the gap to Standard is worth quantifying now that Standard’s numbers have moved. Web is limited to the lesser of 4 sockets or 16 cores with a 64 GB buffer pool, 16 GB of columnstore segment cache and 16 GB of memory-optimized data per database. SQL Server 2025 Standard is the lesser of 4 sockets or 32 cores with 256 GB of buffer pool and 32 GB for each of the other two. Maximum database size is 524 PB on both, so size was never the differentiator.

High availability is the sharper limitation and the one that decides designs. Web edition supports no availability groups and no failover cluster instances. Log shipping is available, database mirroring only as a witness, and replication only as a subscriber for merge, snapshot and transactional replication. If a customer on a hosted plan needs a readable secondary or automatic failover, the plan they are on cannot provide it and no configuration changes that.

There is a pattern that breaks Web edition even where it is still available, and it is worth naming because it arrives gradually. A public site grows an administrative back end that the business also uses to run itself: order processing, stock management, reporting for staff. That is both a technical problem, because the internal workload has different demands from the public one, and a licensing problem, because internal business use falls outside what the edition permits. The correct move at that point is Standard on a properly licensed instance.

Full reference

Where Web edition sat, and where the alternatives sit now

If you are a hosting provider

1. Establish with your SPLA reseller whether SQL Server 2022 Web is still orderable for you. Microsoft’s wording is that it may be available, which is not the same as a guarantee.
2. Work out what your customer plans actually promise. If any of them imply a readable secondary or automatic failover, Web edition never delivered that and 2022 Web still does not.
3. Price SQL Server 2025 Standard per core against continuing on 2022 Web, including the support lifecycle of the older version in the sum.
4. Check that every Web instance is genuinely serving publicly accessible workloads, because the use restriction is the part that fails an audit rather than the core count.
5. Keep reporting monthly on what you deployed. SPLA is a usage-reported programme, and the record is the compliance position.

If you are an end customer

The practical question is worth asking of your host: which edition backs the database in your plan? The answer determines whether a readable secondary is possible, whether availability groups are on the table, and how much memory the instance can cache. It is a reasonable thing to ask before signing, and a plan backed by Web edition has a specific and knowable ceiling rather than an unknown one.

If you are running your own hardware, the two real options have both improved with this release. Express is free and now allows 50 GB per database, which covers a great many small public sites without a licence at all. Standard is the paid answer, and at 32 cores and 256 GB of buffer pool it covers considerably more workload than the edition did two years ago.

What to do with an existing Web edition deployment

• Nothing urgent. An installed SQL Server 2022 Web instance keeps running; what changed is that there is no 2025 successor to move it to.
• Track the support lifecycle of SQL Server 2022 rather than the availability of the edition, because that is the date that will force the decision.
• Plan the destination now: Standard per core for workloads that will grow, Express for the small ones, and a hosted database service if the operational burden is the real problem.
• Do not migrate a Web edition workload onto Standard and keep the same design assumptions. Standard supports basic availability groups and two-node failover clustering, so there are options a Web design would not have considered.
• If an internal business workload crept onto a Web instance at any point, fix that as part of the move rather than carrying it across.

Questions people ask about this