Share via

Disaster recovery license for SQL 2022 WSFC cluster

Rezzani Marco 20 Reputation points
2026-06-08T10:11:50.3233333+00:00

Hi all,

I'm new to SQL, so I'd like to ask you a question about SQL licensing for a DR site.

I have a WSFC for SQL Server 2022 in production with its own license.

My question is: for a possible SQL cluster in the Disaster recovery site, is it possible to reuse the same licenses from production if the DR SQL instance remains powered off and never used except for DR tests? What happens to the production cluster if I insert the same license during cluster installation phase? Will I run into deactivation issues or anything else?

Best regards,

Marco

SQL Server | Other
SQL Server | Other

Additional SQL Server features and topics not covered by specific categories

0 comments

Answer accepted by question author

Marcin Policht 92,380 Reputation points MVP Volunteer Moderator
2026-06-08T11:18:03.1533333+00:00

For SQL Server, the key point is that licensing is generally based on usage rights, not on technical activation. SQL Server 2022 does not behave like Windows desktop software where a product key “deactivates” another installation if reused. In most enterprise deployments, the product key is mainly used during setup, and Microsoft does not automatically shut down or deactivate the production cluster because the same key was entered on another server.

For a Disaster Recovery environment, Microsoft does allow certain passive failover rights, but the details depend on your edition and Software Assurance status. If your production SQL Server licenses include active Software Assurance, you typically get rights to run a passive secondary server for disaster recovery without buying a completely separate SQL Server license for that DR node. The passive DR server must truly be passive except for limited activities such as synchronization, health checks, and periodic DR testing.

If the DR SQL cluster is powered off most of the time and only used during DR exercises or an actual disaster, that generally aligns with Microsoft’s intended passive failover use case. However, there are important limitations. The DR instance cannot be serving production workloads, reporting, analytics, backups for production benefit, or anything considered active usage outside the allowed DR scope. Also, DR testing is allowed only within Microsoft’s permitted testing windows and conditions under Software Assurance.

If you do not have Software Assurance on the production licenses, then failover rights are much more limited, and in many cases the DR environment would require its own licenses even if it stays powered off.

Technically, during installation you can usually enter the same SQL Server product key on the DR cluster without causing activation conflicts or deactivating production. SQL Server itself does not continuously enforce licensing through online activation in the way many consumer products do. The real risk is compliance during a Microsoft license audit, not a technical lockout.

Also keep in mind that for WSFC itself, Windows Server licensing rules are separate from SQL Server licensing. The DR nodes still need proper Windows Server licensing even if SQL licensing is covered through passive failover rights.

The safest approach would be to verify your exact entitlement against Microsoft SQL Server 2022 licensing guide, your Software Assurance agreement, and whether you are using Standard or Enterprise Edition.

Enterprise Edition with Software Assurance is the most common setup for fully covered passive DR rights.

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin

Was this answer helpful?

1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Akhil Gajavelly 1,830 Reputation points Microsoft External Staff Moderator
    2026-06-09T07:03:46.1633333+00:00

    Hi @Rezzani Marco ,

    Thanks for the detailed explanation.

    One additional point to verify is whether your SQL Server 2022 licenses are covered by Software Assurance (SA) or a subscription-based licensing model. The right to run a passive disaster recovery instance without separate SQL Server licenses is generally tied to those benefits.

    Also, if the DR environment is configured as a multi-node WSFC, ensure that all nodes remain within Microsoft's definition of a passive failover environment. Once a DR server starts handling production workloads, reporting, backups for business purposes, or other active operations outside the permitted DR scope, separate licensing may be required.

    From a technical perspective, using the same product key during installation will not deactivate or impact the production cluster. The important consideration is licensing compliance rather than activation.

    I would recommend reviewing your specific licensing agreement or confirming with your Microsoft licensing reseller, as the exact rights can vary depending on edition, licensing program, and SA coverage.

    Thanks,
    Akhil.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.