Share via

To Implement HA strategy require licensing Cost

Sadiq Ali 0 Reputation points
2026-05-05T10:06:08.2233333+00:00

HI Team,

We are planning to implement SQL Server 2025 Enterprise Edition with Always On HA and would like to understand the complete licensing cost, including per-core pricing details.

Could you please assist with this?

Thanks

Sadiq

SQL Server Database Engine
0 comments No comments

3 answers

Sort by: Most helpful
  1. Bruce (SqlWork.com) 83,821 Reputation points
    2026-05-06T00:40:25.6066667+00:00

    In addition, the number of cores needing a license is the max of the number of hardware cores (or vm cores if vm hosted) or 4. If you have SA then passive servers are free. Passive means no read access on the failover servers. If no SA then the failover servers each need a license and allow read access.

    0 comments No comments

  2. Erland Sommarskog 133.9K Reputation points MVP Volunteer Moderator
    2026-05-05T20:17:28.4333333+00:00

    This is a technical forum and not a good place to ask commercial questions. It is better to direct such questions to your local Microsoft representative or a partner. I do see that Q&A Assist AI service has given you answer, but I cannot vouch for its correctness.

    What I do recommend is that you get Software Assurance. This permits you to have a passive node (extra), and good benefits when it's time to upgrade.

    0 comments No comments

  3. Q&A Assist
    2026-05-05T10:06:23.4133333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    For SQL Server 2025 Enterprise Edition with Always On high availability (HA), licensing is per core, and Always On features are included in Enterprise Edition at no extra SQL Server feature cost. The total cost depends on:

    1. How many cores must be licensed
    2. Whether Software Assurance (SA) and/or Azure benefits are used
    3. Whether the replicas are active or passive, and where they run (on-premises vs Azure)

    1. Enterprise Edition core licensing and indicative pricing

    SQL Server Enterprise Edition is licensed per 2‑core pack.

    From the provided pricing examples:

    • Enterprise Edition (2‑core pack): approximately US$15,000+ (exact price depends on region, reseller, and agreement)
    • With Software Assurance, add roughly 25–30% on top of the license price for the SA term (for example, 2 years) if buying perpetual licenses.

    So, for planning purposes only (non-binding, approximate):

    • 2 cores Enterprise: ~US$15,000+ (license only)
    • 4 cores Enterprise: ~2 × 2‑core packs ≈ US$30,000+
    • 8 cores Enterprise: ~4 × 2‑core packs ≈ US$60,000+

    For precise commercial pricing, a Microsoft licensing partner or reseller must be consulted.

    2. Always On HA features and edition

    For SQL Server 2025:

    • Always On availability groups (full AGs) are supported in Enterprise only.
    • Basic availability groups are supported in Standard only.

    Since the plan is Enterprise Edition with Always On HA, the correct edition for full AG capabilities is Enterprise.

    Relevant HA features in Enterprise include:

    • Always On availability groups
    • Contained availability groups
    • Distributed availability groups
    • Automatic read/write connection rerouting
    • Advanced online operations (online index operations, online schema change, etc.)

    These features are part of Enterprise Edition and do not have separate feature surcharges; the cost impact is through the Enterprise per‑core licensing.

    3. HA/DR licensing considerations (on-premises vs Azure)

    If HA is implemented on Azure SQL VMs instead of purely on-premises, there are additional cost-optimization options:

    • With Software Assurance, it is possible to implement HA/DR with SQL Server on Azure VMs without extra SQL Server licensing cost for passive DR instances. This applies when using SQL Server licenses with SA and Azure Hybrid Benefit.
    • There is also a free DR replica in Azure benefit: with SA, a passive DR replica in Azure can be configured without additional SQL Server license cost for that passive node. When all replicas are in Azure and using pay‑as‑you‑go licensing, customers can also be entitled to license‑free passive replicas when configured as HA/DR.

    If using pay‑as‑you‑go SQL Server on Azure VMs instead of bringing licenses:

    • The SQL Server license cost is included in the per‑second VM price and depends on the number of vCPUs and the edition (Web, Standard, Enterprise).
    • This model is often better for workloads with unknown lifetime or variable scale.

    4. Developer and lightweight scenarios

    For non-production environments (dev/test, PoC) related to the HA design:

    • SQL Server Developer Edition is free and has all Enterprise features, including Always On, but is not allowed for production.
    • SQL Server Express Edition is also free and allowed for lightweight production workloads, but many Enterprise-level HA/DR features are not available, so it is not suitable for an Enterprise Always On design.

    To obtain a complete and accurate licensing cost for the Always On HA deployment:

    1. Determine the total number of physical or virtual cores that will run production Enterprise instances (including HA replicas that are active/primary or readable secondaries).
    2. Decide whether to:
      • Purchase perpetual Enterprise core licenses with SA, or
      • Use subscription/CSP or pay‑as‑you‑go models (for example, Azure VMs), or
      • Use Azure Hybrid Benefit if existing licenses with SA are available.
    3. Engage a Microsoft licensing partner or reseller with the core counts and HA topology (number of replicas, which are active vs passive, on-prem vs Azure) to get exact pricing for:
      • Enterprise Edition per 2‑core pack
      • Software Assurance add‑on
      • Any Azure VM/pay‑as‑you‑go costs if applicable.

    References:

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.