Need clarity on SQL Server Always On Licensing

Question

Need clarity on SQL Server Always On Licensing

karna sharath kumar Reddy 0

Hi there!

I have a query regarding the licensing and configuration requirements for SQL Server Always On High Availability.

One of our clients has procured SQL Server Enterprise Edition with Software Assurance, with a 1 × 2-core license pack.

The client’s requirement is to configure an Always On Availability Group with the following architecture:

1 Primary Replica
1 Secondary Replica
1 DR Replica, located in the IBRI region

Could you please confirm whether this configuration is supported and properly licensed with the 1 × 2-core SQL Server Enterprise license pack with Software Assurance?

If yes, could you please explain how the licensing would apply to the primary, secondary, and DR replicas, including any Software Assurance benefits or licensing considerations for the passive/DR replicas?

If additional licenses or cores are required, please clarify the minimum licensing required for this architecture.
Microsoft SQL Server 7JQ‑XXXXX Licensing & DR Usage Guide

1. SKU Overview

The Microsoft SKU 7JQ‑XXXXX corresponds to SQL Server Enterprise Core Edition (2‑Core License Pack with Software Assurance). This license pack allows enterprise‑level deployment with full feature access, supporting large‑scale, mission‑critical workloads.

2. Core Licensing Rules

• All physical or virtual cores used by SQL Server must be licensed.

• Each 7JQ‑XXXXX pack covers 2 cores; licenses are sold in pairs.

• Enterprise edition is only available under core‑based licensing (no CALs).

• Software Assurance (SA) adds benefits like passive failover rights and version upgrades.

3. Active/Passive Server Licensing

With Software Assurance, you can have one passive SQL Server instance (of equal or lesser size) without extra licenses, as long as it remains truly passive — not serving queries, users, or transactions under normal operation.

4. Disaster Recovery (DR) Usage

You may maintain one cold standby or DR instance without licensing if it is not used actively. If the DR node handles reporting, backups, or read‑only queries, it becomes active and must be fully licensed.

5. Virtualization Scenarios

If you license all physical cores on a host with Enterprise + SA, you gain unlimited virtualization rights. Otherwise, you must license each virtual core (minimum of 4 per VM). Passive or DR virtual servers follow the same passive‑use rules.

6. Summary

• SKU 7JQ‑XXXXX = SQL Server Enterprise Core + SA (2‑core pack)

• Core‑based licensing model; no CALs needed

• SA permits one passive/failover instance for free (if truly passive)

• DR servers must be licensed if used actively

• Enterprise + SA can unlock unlimited virtualization

Always confirm compliance with Microsoft Product Terms and your regional licensing agreement.

Dan Guzman 9,521 Reputation points

2026-09-15T13:05:12.64+00:00

An important consideration for licensing is whether the secondary replica is used for purposes other than just HA as called out it #3. In other words, if the secondary replica services read or read/write workloads, those cores are not covered by the main replica license and must be purchased separately.

2 answers

Your answer

Dan Guzman 9,521 Reputation points

2026-09-15T13:05:12.64+00:00

An important consideration for licensing is whether the secondary replica is used for purposes other than just HA as called out it #3. In other words, if the secondary replica services read or read/write workloads, those cores are not covered by the main replica license and must be purchased separately.

Answer 1

Bruce (SqlWork.com) 85,441

Unless you are hosting in a 2 core vm, you need enough 2 core packs to cover all the physical cores of the host. Also 4 cores are the minimum even if using a 2 core vm.

0 comments

Answer 2

Beware that this is a technical forum, and your question is about legal matters. You cannot get authoritative answers here. That is, you may get answers. However, if your client is license-audited and points out that they are incorrectly licensed and your client refers to this thread, that is not going to change the opinion of the license auditor.

For an authoritative answer, I primarily recommend you to read the SQL Server Licensing Guide Since I work in a developer role, I never have reasons to consider licensing, so I certainly do not it by heart. But I have a recollection of that the scenario you describe is covered there, and the configuration you described is indeed permitted with Enterprise Edition with Software Assurance. But that is from memory, so you need read the Licensing Guide yourself.

If you don't find questions to all your answers in the Licensing Guide, I recommend that you contact your local Microsoft representative. What you need is something in writing that you can present for a license auditor when that day comes. The license auditor may still disagree, but he or she is likely to be more benevolent if it is clear that you have handled in good faith.