Is it possible to join new node SQL in Failover cluster with different Edition? As example:

Cluster Failover running based on SQL Enterprise Evaluation Edition add a new node based on SQL Standard Edition

  • 1
    Let us know after you try it.
    – user507
    Commented Mar 20, 2017 at 14:17

2 Answers 2


I've never tried this but I'm reliably informed it is 100% not possible. It is certainly not supported by Microsoft, for good reason, so why would you do it?

The SQL Server edition you are installing must match across all the nodes in a SQL Server failover cluster. When you add a new node to an existing SQL Server failover cluster, make sure that you specify that the edition matches the edition of the existing failover cluster.

This comes from this MSDN link found almost instantly after a quick web search.

Bear in mind there are a few obvious and not-so-obvious functional reasons why you would not want to failover from Enterprise to Standard as some features are not supported in both.

The idea of a clustered environment should be that you maintain integrity of the database environment upon failover, so why compromise that in any way, whether talking about support or features?

  • You can edit your answer. It is not possible, the installer will stop you from adding a node that is not the same edition.
    – Spörri
    Commented Mar 20, 2017 at 15:17

This should be possible.

However, do note that some features that are present in Enterprise Editions may not be available in Standard Editions. This can cause severe application issues when a Failover occurs.

I suppose, a Standard edition may be used on an Always-On Secondary Replica where Reporting is offloaded and it does not ideally act as a Failover node. In any case, please test out your solution before taking it forward on Production.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.