Microsoft SQL Server 2025 Failover Rights – staying or going?


Microsoft released SQL Server 2025 on November 18th 2025 and updated the Product Terms. However, the update has caused confusion and consternation amongst the Microsoft community – as it seems to suggest that failover rights as a Software Assurance benefit have been removed!!! 😱 (Spoiler alert – it’s almost certain they haven’t).

If you’re not familiar with this right it means, in a nutshell, that organisations who purchase SQL Server licenses with Software Assurance (SA) may license additional servers at no extra cost, as long as those servers are used only for disaster recovery/failover purposes. This is a long standing and widely used benefit – removing this right will mean one of 2 things:

  • Organisations’ SQL Server licensing will double/triple by millions of £/$/€ more per year
  • Organisations will be forced to have less resilient SQL Server systems, potentially leading to more downtime and lost revenue

Ultimately, if either of those were the case, I believe it would lead to a mass exodus of SQL Server customers. Microsoft may hope they would move to SQL Azure/SQL Server enabled by Azure Arc but I’d expect many to explore other options – Oracle, Postgres, Amazon RDS etc.

Largely because of that, and the fact that we have seen an increase in Product Terms errors over the last couple of years, I’m of the opinion that it is an error and will – eventually – be corrected…but it is worth looking at anyway.

As I was about to press publish, Peter Van Uden has commented on LinkedIn that he’s had confirmation that it is an error and will be corrected in the coming days.

Fellow Microsoft watcher Alex Golev noticed that the whole section had been deleted without replacement:

Other parts of the Product Terms still refer to this section which suggests this is an erroneous deletion…but it could also mean that they just didn’t edit those sections correctly.

This Microsoft page – https://www.microsoft.com/licensing/guidance/SQL?msockid=144db73d53b469e721fda347528468b6 which is licensing guidance for SQL Server 2025 still contains the failover rights information:

I genuinely believe this is an error. It is a huge change that would have significant consequences for most Microsoft customers, including their largest and most significant customers. Making this change would be an enormous risk and to do so without any official announcement or warning is unbelievable. I’m sure we’ll see a reversal in the coming days and that’s why I haven’t posted about this already.

However, I feel it does highlight the increasingly slapdash approach that has been taken to the Microsoft Product Terms since it became an online site, rather than document downloads. It seems likely to me that updates are being made by people with little understanding of software licensing and so they don’t see the consequence of their actions.

The fact that it’s 4 days since this change was made and there has been no word from Microsoft is disappointing – but hopefully that correction will appear soon.

So, don’t panic but do remember that these things happen and that Microsoft experts like me, Alex, Peter and more can be very useful in these scenarios. 😁

Update: The missing text has been reinstated so the panic is over. It does highlight the need for us all to be vigilant in the future though.

Microsoft SQL Server 2025 – what’s new


SQL Server 2025 has been released and, while the licensing model remains the same, there are few changes worthy of note:

  • Developer now comes in “Standard” and “Enterprise” versions.
  • SQL Server Standard max compute capacity per instance increased from 24 to 32 cores
  • SQL Server Standard max buffer memory increased from 128GB to 256GB
  • SQL Server Express now supports a 50GB database size

The first will help with a common problem. With just a single Developer product, it contained all the features of both SQL Server Standard and Enterprise; often I see scenarios where a product/system was inadvertently created with a dependency on an Enterprise feature…hugely increasing the required licensing costs. As you can see, the price difference between Standard and Enterprise is significant:

https://cdn-dynmedia-1.microsoft.com/is/content/microsoftcorp/microsoft/bade/documents/products-and-services/en-us/cloud/SQL-Server-2025-Pricing.pdf

That price difference is also why the changes to maximums for compute capacity and memory are important. The increased allowances may mean that some SQL Server Enterprise scenarios within your environment could be migrate to Standard edition with a 2025 upgrade. If it’s a 32 core setup, that’s a $176,000 reduction.

Finally, the increased database size for SQL Server 2025 Express may increase its viability for production scenarios – although it retains the single CPU limit.

See a comprehensive list of features here – Editions and Supported Features of SQL Server 2025 – SQL Server | Microsoft Learn

Another change is that SSRS (SQL Server Reporting Services) is now replaced with PBIRS (Power BI Reporting Services). 

PBIRS is available to customers with SQL Server 2025 Standard and Enterprise but for prior versions, PBIRS is SQL Enterprise only and only with active SA.