Clarification Required – SQL Server Enterprise Licensing for Physical Migration, Always On HA and Read-Only Routing

Abdur Rahman M 20 Reputation points
2026-11-16T07:11:22.2733333+00:00

Dear Microsoft Licensing Team,

We are planning to migrate our existing SQL Server production environment from a virtual machine to new physical servers and implement SQL Server Always On Availability Groups.

We currently have SQL Server 2019 Enterprise Edition with 12-core licensing on our existing production VM. The environment hosts one large production database along with several smaller databases.

Our proposed migration and licensing requirements are as follows:

1. Production Migration

  • We plan to transfer the large production database to a new physical server.
  • The new physical server will use SQL Server 2019 Enterprise Edition.
  • We intend to utilize our existing 12-core Enterprise licenses for this new physical production server, subject to the applicable license reassignment rights.
  • After migration, the existing production VM will retain only smaller databases (approximately 5 GB, 8 GB and 10 GB).

2. Always On High Availability

  • We plan to implement a two-node Always On Availability Group using two physical servers.
  • The primary server will host the production database.
  • The secondary server will be configured for synchronous replication and automatic failover.

3. Existing UAT Licenses

  • We currently have SQL Server 2022 Enterprise Edition licenses allocated to our UAT environment.
  • The available licensing allocation consists of 2 cores currently assigned to UAT and another 2-core allocation that we understand is unused.
  • We would like to understand whether these existing SQL Server 2022 Enterprise licenses can be reassigned and utilized for the existing production VM which using currently 12 core
  • 4. Read-Only Routing and Reporting Workloads

We also intend to enable Always On read-only routing on the secondary replica so that Power BI and SSRS developers can execute reporting queries against the secondary database without impacting the primary production workload.

We require clarification on the following licensing questions:

  1. Can our existing 12-core SQL Server 2019 Enterprise license be reassigned from the production VM to the new 12-core physical server?
  2. If the primary server is covered by active Software Assurance, can the secondary server operate as a passive HA replica without requiring additional SQL Server core licenses?
  3. If we enable read-only routing and allow Power BI/SSRS developers to execute reporting queries against the secondary replica, will the secondary server require separate SQL Server Enterprise core licensing?
  4. Can the existing 12-core license be utilized for the primary server while the existing production VM continues hosting the smaller databases? If not, what is the minimum additional licensing requirement for the old VM?
  5. Is there any specific Software Assurance requirement or licensing benefit applicable to our proposed two-node Always On HA configuration with read-only reporting?
  6. Are there any additional licensing requirements for Power BI Report Server or SSRS when reporting workloads connect to the readable secondary replica?

We request your confirmation of the applicable licensing requirements and the minimum additional core licenses, if any, required for this architecture.

Please provide your clarification based on our existing SQL Server 2019 enterprise  (12 cores) and SQL Server 2022 Enterprise(2 core assigned to UAT and 2 core unused) licensing entitlements so that we can finalize the migration and HA implementation without licensing compliance issues.

Thank you for your support.

Best regards, DBA Team

 

Dear Microsoft Licensing Team,

We are planning to migrate our existing SQL Server production environment from a virtual machine to new physical servers and implement SQL Server Always On Availability Groups.

We currently have SQL Server 2019 Enterprise Edition with 12-core licensing on our existing production VM. The environment hosts one large production database along with several smaller databases.

Our proposed migration and licensing requirements are as follows:

1. Production Migration

  • We plan to transfer the large production database to a new physical server.
  • The new physical server will use SQL Server 2019 Enterprise Edition.
  • We intend to utilize our existing 12-core Enterprise licenses for this new physical production server, subject to the applicable license reassignment rights.
  • After migration, the existing production VM will retain only smaller databases (approximately 5 GB, 8 GB and 10 GB).

2. Always On High Availability

  • We plan to implement a two-node Always On Availability Group using two physical servers.
  • The primary server will host the production database.
  • The secondary server will be configured for synchronous replication and automatic failover.

3. Existing UAT Licenses

  • We currently have SQL Server 2022 Enterprise Edition licenses allocated to our UAT environment.
  • The available licensing allocation consists of 2 cores currently assigned to UAT and another 2-core allocation that we understand is unused.
  • We would like to understand whether these existing SQL Server 2022 Enterprise licenses can be reassigned and utilized for the existing production VM which using currently 12 core
  • 4. Read-Only Routing and Reporting Workloads

We also intend to enable Always On read-only routing on the secondary replica so that Power BI and SSRS developers can execute reporting queries against the secondary database without impacting the primary production workload.

We require clarification on the following licensing questions:

  1. Can our existing 12-core SQL Server 2019 Enterprise license be reassigned from the production VM to the new 12-core physical server?
  2. If the primary server is covered by active Software Assurance, can the secondary server operate as a passive HA replica without requiring additional SQL Server core licenses?
  3. If we enable read-only routing and allow Power BI/SSRS developers to execute reporting queries against the secondary replica, will the secondary server require separate SQL Server Enterprise core licensing?
  4. Can the existing 12-core license be utilized for the primary server while the existing production VM continues hosting the smaller databases? If not, what is the minimum additional licensing requirement for the old VM?
  5. Is there any specific Software Assurance requirement or licensing benefit applicable to our proposed two-node Always On HA configuration with read-only reporting?
  6. Are there any additional licensing requirements for Power BI Report Server or SSRS when reporting workloads connect to the readable secondary replica?

We request your confirmation of the applicable licensing requirements and the minimum additional core licenses, if any, required for this architecture.

Please provide your clarification based on our existing SQL Server 2019 enterprise  (12 cores) and SQL Server 2022 Enterprise(2 core assigned to UAT and 2 core unused) licensing entitlements so that we can finalize the migration and HA implementation without licensing compliance issues.

Thank you for your support.

Best regards,
DBA Team

 

SQL Server Database Engine

4 answers

Sort by: Most helpful
  1. Erland Sommarskog 137.7K Reputation points MVP Volunteer Moderator
    2026-11-16T14:25:49.37+00:00

    First of all: This is a technical forum, and your questions are of a legal nature. You cannot get authoritative answers here. We can give advice, but if you go ahead and you are later license-audited, and the license auditor says that you are incorrectly licensed, referring to a forum thread like this one, will carry very little weight. For authoritative answers, you need contact your local Microsoft representative, and make sure that you get answers in writing, so that you have something to show the license auditor.

    Next: If you have not read the SQL Server Licensing Guide, do so. I believe that it will answer a few of your questions. Although, this link goes to the guide for SQL 2022, and I believe they did some changes from SQL 2019 to SQL 2022, to the advantage for the customer. But if I understand it correctly, the license you have is for SQL 2022, and in that case, the Licensing Guide will apply, I assume.

    Then: From a technical perspective, I would question that you are migrating from a VM to a physical machine and stay on SQL 2019, a version that is out of mainstream support. I would recommend that you upgrade to SQL 2025. But obviously, this comes with a license cost, although this reduced as you have SA.

    I will now try to answer your questions, but beware the caveat above. And I did not read the License Guide in detail to check things up.

    Can our existing 12-core SQL Server 2019 Enterprise license be reassigned from the production VM to the new 12-core physical server?

    I like to believe so. But that is based on common sense (which does not always apply when it comes to licensing!)

    If the primary server is covered by active Software Assurance, can the secondary server operate as a passive HA replica without requiring additional SQL Server core licenses?

    As long as it is passive, yes. The license guide lists a few things you can do on the passive replica.

    If we enable read-only routing and allow Power BI/SSRS developers to execute reporting queries against the secondary replica, will the secondary server require separate SQL Server Enterprise core licensing?

    Yes, a readable secondary must be licensed separately.

    Can the existing 12-core license be utilized for the primary server while the existing production VM continues hosting the smaller databases? If not, what is the minimum additional licensing requirement for the old VM?

    If you transfer the license to the new physical machine, the instance on the VM will be unlicensed, so you will need to get a new license. Now, since these databases are small, you could opt for SQL Server 2025 Express Edition, which is free. Since one of the databases is 10 GB, you will need SQL 2025 where the cap for the database size is 50 GB, as opposed to 10 GB for SQL 2019 and SQL 2022.

    Would you need features/capabilities not available in Express Edition for these databases, you will have no choice but to cough up the money for a new license for the VM.

    Is there any specific Software Assurance requirement or licensing benefit applicable to our proposed two-node Always On HA configuration with read-only reporting?

    No, I don' think so. SA permits you have one more DR copy, but as I recall, and active read-only instance requires full licensing. Again, check the Licensing Guide.

    Are there any additional licensing requirements for Power BI Report Server or SSRS when reporting workloads connect to the readable secondary replica?

    Again, the readable secondary must be licensed, and if PBIRS/SSRS is running on a separate machine that server must also be licensed.

    Was this answer helpful?

    0 comments No comments

  2. Ntiganzwa Kagimba Theophile 0 Reputation points
    2026-11-16T08:39:03.05+00:00

    Hello Abdur Rahman,

    Here are the direct answers to both of your follow-up questions so your team can finalize the exact license counts:

    1. Secondary Reporting Replica: Core-Based vs. User-Based & Core Count

    • License Model: You must purchase Core-Based licenses. SQL Server Enterprise Edition is only sold under the Per-Core licensing model (Microsoft does not offer a Server + User/CAL model for Enterprise Edition, and Always On Availability Groups with readable secondaries require Enterprise Edition).
    • How Many Cores to Buy: You must license 100% of the physical cores on the secondary server, subject to a minimum of 4 core licenses per physical processor (socket).
      • Does it have to match production? Not strictly by rule, only by hardware. Licensing is tied to the physical hardware of the secondary server itself, not the primary server's license count.
        • For example, if your primary server has 12 physical cores and your secondary server also has 12 physical cores, then yes, you need 12 Enterprise core licenses for the secondary. However, if your secondary physical server has 8 physical cores (e.g., 1 processor with 8 cores), you would only need 8 Enterprise core licenses to cover it.

    2. Existing Production VM: How Many Cores Are Needed for Very Small Databases?

    • Database size does not affect licensing: Microsoft licenses SQL Server strictly based on compute resources (virtual cores / vCPUs) assigned to the VM, regardless of whether the databases inside are 5 GB or 5 TB.
    • The Minimum Requirement: When licensing an individual VM by virtual cores, Microsoft enforces a strict minimum of 4 core licenses per VM (or the exact number of vCPUs assigned to that VM, whichever is higher).
    • Important Rule on VM Core Licensing: Since SQL Server 2022, licensing an individual VM by its vCores requires your core licenses to either have active Software Assurance (SA) or be Subscription licenses. (Without SA or a subscription, you cannot license a VM by vCPU count alone—you would have to license the underlying physical host instead).

    What this means for your VM right now:

    1. Scale down the VM: Since the remaining databases are small (5 GB, 8 GB, and 10 GB), reduce the VM's allocated vCPUs in your hypervisor from 12 vCPUs down to 4 vCPUs.
    2. Required License Count: You will need 4 core licenses total for that VM.
    3. Using your existing SQL 2022 Enterprise cores: Assuming your 4 cores of SQL Server 2022 Enterprise (2 unused + 2 reassigned from UAT) carry active SA or are subscription licenses, those 4 cores will cover this VM completely at 0 additional license cost. (If they do not have active SA, you can alternatively purchase 4 cores of SQL Server Standard Edition with SA/subscription—which is roughly 75% cheaper than Enterprise—as long as those small databases do not rely on Enterprise-only features).

    Let me know the physical core count of your secondary server and whether your SQL 2022 Enterprise licenses have active Software Assurance, and we can confirm your exact final numbers!

    Best regards,

    Microsoft Licensing & Architecture SupportHello Abdur Rahman,

    Here are the direct answers to both of your follow-up questions so your team can finalize the exact license counts:

    1. Secondary Reporting Replica: Core-Based vs. User-Based & Core Count

    • License Model: You must purchase Core-Based licenses. SQL Server Enterprise Edition is only sold under the Per-Core licensing model (Microsoft does not offer a Server + User/CAL model for Enterprise Edition, and Always On Availability Groups with readable secondaries require Enterprise Edition).
    • How Many Cores to Buy: You must license 100% of the physical cores on the secondary server, subject to a minimum of 4 core licenses per physical processor (socket).
      • Does it have to match production? Not strictly by rule, only by hardware. Licensing is tied to the physical hardware of the secondary server itself, not the primary server's license count.
        • For example, if your primary server has 12 physical cores and your secondary server also has 12 physical cores, then yes, you need 12 Enterprise core licenses for the secondary. However, if your secondary physical server has 8 physical cores (e.g., 1 processor with 8 cores), you would only need 8 Enterprise core licenses to cover it.

    2. Existing Production VM: How Many Cores Are Needed for Very Small Databases?

    • Database size does not affect licensing: Microsoft licenses SQL Server strictly based on compute resources (virtual cores / vCPUs) assigned to the VM, regardless of whether the databases inside are 5 GB or 5 TB.
    • The Minimum Requirement: When licensing an individual VM by virtual cores, Microsoft enforces a strict minimum of 4 core licenses per VM (or the exact number of vCPUs assigned to that VM, whichever is higher).
    • Important Rule on VM Core Licensing: Since SQL Server 2022, licensing an individual VM by its vCores requires your core licenses to either have active Software Assurance (SA) or be Subscription licenses. (Without SA or a subscription, you cannot license a VM by vCPU count alone—you would have to license the underlying physical host instead).

    What this means for your VM right now:

    1. Scale down the VM: Since the remaining databases are small (5 GB, 8 GB, and 10 GB), reduce the VM's allocated vCPUs in your hypervisor from 12 vCPUs down to 4 vCPUs.
    2. Required License Count: You will need 4 core licenses total for that VM.
    3. Using your existing SQL 2022 Enterprise cores: Assuming your 4 cores of SQL Server 2022 Enterprise (2 unused + 2 reassigned from UAT) carry active SA or are subscription licenses, those 4 cores will cover this VM completely at 0 additional license cost. (If they do not have active SA, you can alternatively purchase 4 cores of SQL Server Standard Edition with SA/subscription—which is roughly 75% cheaper than Enterprise—as long as those small databases do not rely on Enterprise-only features).

    Let me know the physical core count of your secondary server and whether your SQL 2022 Enterprise licenses have active Software Assurance, and we can confirm your exact final numbers!

    Best regards,

    Microsoft Licensing & Architecture Support

    Was this answer helpful?

    0 comments No comments

  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  4. AI answer

    2026-11-16T07:12:40.1966667+00:00

    A secondary replica used by Power BI or SSRS for read-only queries is an active SQL Server workload and must be licensed separately; the Software Assurance passive-failover benefit does not cover that use.

    Licensing outcome for the proposed design

    Component Required treatment
    New physical primary License every physical core, subject to at least four core licenses per physical processor. The existing 12 licenses suffice only if that calculation requires no more than 12.
    Physical secondary, strictly passive May qualify for the HA/DR benefit while the corresponding primary licenses have active Software Assurance or subscription coverage.
    Physical secondary serving reports Fully license its physical cores; it is no longer passive.
    Existing production VM retaining databases License separately by all vCores allocated to the VM, with a four-core minimum per VM.
    SQL Server 2022 Enterprise licenses used for SQL Server 2019 Potentially allowed through downgrade rights, depending on the purchase channel and agreement.
    Power BI Report Server For SQL Server 2022 and earlier, requires Enterprise core licenses with active SA.
    Power BI/SSRS clients querying SQL Server Their connections do not create a separate SQL Server licensing model, but they make a passive secondary active.

    1. Reassigning the existing 12 SQL Server 2019 core licenses

    You can reassign the 12 licenses from the VM to the new physical server only if:

    1. Your licensing agreement permits the reassignment at that time.
    2. The licenses are removed from the old VM.
    3. Twelve licenses cover the new server’s required physical-core count.

    For SQL Server installed directly on a physical server, all physical cores must be licensed, regardless of how many cores SQL Server actually uses. The licensing guide states a minimum of four core licenses per physical processor.^1^

    Examples:

    • One 12-core processor: 12 core licenses.
    • Two 6-core processors: 12 core licenses.
    • Two processors with only two active cores each: eight licenses because each processor has a four-core minimum.
    • A 16-core server: 16 licenses, even if SQL Server affinity is limited to 12 cores.

    Standard on-premises reassignment is generally subject to the 90-day rule. Active SA can provide additional reassignment flexibility in eligible scenarios, including movement within the same server farm; check the current Product Terms and your agreement before moving the assignment.^2^

    The cited 180-day dual-use migration benefit is documented for migrations to Azure, not as a general entitlement for a physical-to-physical on-premises migration.^3^ Do not assume that the same 12 licenses can cover both on-premises systems during migration unless your agreement or licensing provider confirms a separate migration allowance.

    2. Passive Always On secondary with Software Assurance

    SQL Server licenses with active SA or subscription coverage include an HA/DR benefit for qualifying passive instances.^4^ SQL Server 2019 Enterprise supports Always On availability groups and identifies failover-server rights as requiring SA.^5^

    A qualifying AG secondary must not serve user workloads:

    • A non-readable secondary can qualify.
    • A readable secondary can qualify only while it has no active user connections.
    • A readable secondary with connected users does not qualify.
    • Standalone databases or associated active SQL services in the same operating-system environment can also disqualify it.^4^

    Synchronous replication and automatic failover do not by themselves make the secondary active. Reporting connections do.

    3. Read-only routing

    Once Power BI, SSRS, developers, or other users run queries against the secondary, license that physical secondary independently for all its physical cores, including the per-processor minimum. Read-only intent does not preserve passive status.

    Therefore, the practical choices are:

    • Free passive HA secondary: prevent reporting/user connections.
    • Readable reporting secondary: purchase or assign enough Enterprise core licenses to cover it fully.
    • Separate reporting system: license that system independently and keep the AG secondary passive.

    4. Existing VM and the 2-core allocations

    The 12 licenses cannot simultaneously cover the new physical primary and the old VM once both run production databases. Database size is irrelevant to core licensing.

    The old VM requires licenses for every allocated vCore, subject to a four-core minimum per VM.^6^ Thus:

    • 2-vCore VM → minimum 4 core licenses.
    • 4-vCore VM → 4 core licenses.
    • 12-vCore VM → 12 core licenses.

    Your two 2-core SQL Server 2022 Enterprise allocations could total the four-core VM minimum only if:

    1. Both are transferable core-license entitlements.
    2. The UAT-assigned pair is validly reassigned under your agreement.
    3. They are not simultaneously used for UAT.
    4. Their purchase channel grants downgrade rights to SQL Server 2019.

    Commercial Licensing server licenses include downgrade rights, allowing an earlier version of the same product to be used instead of the licensed version.^7^ If the UAT server continues running SQL Server, its assigned licenses cannot also license the production VM.

    5. Power BI Report Server and SSRS

    Connecting a separately licensed Power BI or SSRS service to SQL Server does not eliminate the need to license the readable SQL secondary.

    For Power BI Report Server with SQL Server 2019/2022 Enterprise, usage rights require Enterprise core licenses with active SA and expire when SA expires.^8^ A Power BI Pro license is required to publish Power BI reports to PBIRS under the SQL Server licensing route, but not merely to view and interact with reports.

    SSRS/PBIRS installation, report-server database, and publishing rights are separate from the Database Engine licensing calculation. The supported report-server database editions depend on the report-server edition.^9^

    Minimum indicated by the stated architecture

    Assuming the primary physical server has exactly 12 licensable cores:

    • Primary: existing 12 Enterprise core licenses.
    • Secondary used only for passive HA: potentially zero additional SQL licenses, while matching SA remains active and all passive conditions are met.
    • Secondary used for reporting: enough Enterprise core licenses for every physical core on that server.
    • Old VM retained with production databases: at least four Enterprise core licenses if reduced to four or fewer vCores; otherwise one license per allocated vCore.

    Obtain written confirmation from your Microsoft licensing reseller or account representative using the processor/core topology, VM vCPU configuration, purchase channel, license statements, SA expiration dates, and server-farm locations. Those facts determine whether the proposed reassignment and downgrade rights are currently available.


    References

    1. Microsoft SQL Server 2022 Licensing guide
    2. Microsoft Product Terms
    3. Azure Hybrid Benefit - Azure SQL Database & SQL Managed Instance
    4. Manage licensing and billing of SQL Server enabled by Azure Arc
    5. Editions and supported features of SQL Server 2019
    6. License SQL Server, Windows Server, and Linux in Azure VMware Solution
    7. Downgrade Rights Licensing Guidance - microsoft.com
    8. What is Power BI Report Server?
    9. SQL Server Reporting Services features supported by editions
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.