Core component of SQL Server for storing, processing, and securing data
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:
- Your licensing agreement permits the reassignment at that time.
- The licenses are removed from the old VM.
- 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:
- Both are transferable core-license entitlements.
- The UAT-assigned pair is validly reassigned under your agreement.
- They are not simultaneously used for UAT.
- 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
- Microsoft SQL Server 2022 Licensing guide
- Microsoft Product Terms
- Azure Hybrid Benefit - Azure SQL Database & SQL Managed Instance
- Manage licensing and billing of SQL Server enabled by Azure Arc
- Editions and supported features of SQL Server 2019
- License SQL Server, Windows Server, and Linux in Azure VMware Solution
- Downgrade Rights Licensing Guidance - microsoft.com
- What is Power BI Report Server?
- SQL Server Reporting Services features supported by editions