What Is Software Assurance for SQL Server?
Software Assurance is an annual maintenance programme purchased with (or added to) SQL Server licences through Microsoft Volume Licensing. The typical cost is approximately 25 % of the licence price per year — for SQL Server Enterprise at $14,256 per core, SA costs roughly $3,564 per core annually. In return, SA provides a comprehensive set of usage rights, deployment flexibility, and support services that extend far beyond the base licence.
Core SA Benefits
SA delivers eight major categories of benefit: (1) version upgrade rights to new SQL Server releases, (2) licence mobility across servers and cloud providers, (3) unlimited virtualisation on Enterprise Edition, (4) passive failover rights for DR, (5) Azure Hybrid Benefit for cloud cost reduction, (6) per-VM licensing in virtualised environments (SQL 2022+), (7) step-up rights from Standard to Enterprise, and (8) planning services, training vouchers, and support incidents. Most organisations actively use 2–3 of these. The goal is to activate all applicable benefits.
ROI Framework
SA pays for itself when the combined value of benefits used exceeds the annual SA fee. For a 100-core SQL Enterprise deployment: SA costs ~$356K/year. If you use AHB on 50 Azure VMs (saving $750K/year), exercise passive failover (avoiding $713K in DR licences), and upgrade from SQL 2019 to 2022 (avoiding $1.4M in new licences), the benefit exceeds $2.8M against $356K in SA cost — an 8× return. Even using just one major benefit typically justifies SA renewal.
Benefit 1 — Version Upgrade Rights
With active SA, you can upgrade to any new major version of SQL Server released during your SA coverage period without purchasing new licences. This is the foundational SA benefit and often the simplest to quantify.
How It Works
If you purchased SQL Server 2019 with SA and Microsoft releases SQL Server 2022, you can upgrade all SA-covered instances to 2022 at no additional licence cost. The SA fee you pay annually effectively amortises the cost of future versions. Over a typical 3–5 year upgrade cycle, SA's cumulative annual cost is significantly less than purchasing new licences for the latest version. For 100 cores of Enterprise: new licence purchase would cost $1.4M; three years of SA costs $1.07M — a $350K saving plus you retain the ongoing benefits. The strategic value: you can adopt new features (improved security, performance, analytics) immediately rather than waiting for budget approval for new licences.
Timing Strategy
If your SA is expiring and a new SQL Server version has been announced, upgrade before SA expires. Once you upgrade under active SA, you retain the perpetual licence for that version — even if you subsequently let SA lapse. This "lock in the latest version" strategy ensures you get maximum value from your final SA period. Conversely, if SA lapses before you upgrade, you are permanently locked to the version you had when SA was last active. Re-acquiring SA after a lapse typically requires repurchasing the underlying licence at current list price — a significantly more expensive path than maintaining continuous SA coverage.
Benefit 2 — Licence Mobility
Licence Mobility overrides the 90-day reassignment restriction, allowing SA-covered SQL Server licences to move freely between servers within a server farm and to authorised cloud providers.
Within Your Data Centre
SA-covered licences can be reassigned to any server within the server farm at any time — no 90-day waiting period. A "server farm" is servers in the same data centre or two data centres in the same time zone region. This is essential for virtualised environments: VMs with SQL Server can migrate between hosts via vMotion or Live Migration without compliance violations. Without SA, every potential destination host must be independently licensed — or you violate the 90-day rule. For dynamic environments with automated VM placement (DRS, SCVMM), SA licence mobility is functionally mandatory.
To Azure, AWS, and Authorised Providers
SA enables Bring Your Own Licence to cloud providers: deploy SQL Server on AWS EC2 (dedicated tenancy, requires Licence Mobility Verification Form), Azure VMs (via Azure Hybrid Benefit), or other authorised hosting providers. This means idle on-premises licences can be redeployed to cloud infrastructure — avoiding the cloud provider's SQL Server surcharge. For hybrid and cloudburst scenarios, licence mobility provides the legal framework to move workloads between on-premises and cloud as demand fluctuates, without purchasing separate cloud-specific licences.
Benefit 3 — Unlimited Virtualisation (Enterprise + SA)
The highest-impact SA benefit for heavily virtualised environments: SQL Server Enterprise with SA grants unlimited virtualisation rights on a fully licensed host.
| Scenario | Without SA | With Enterprise + SA | Savings |
|---|---|---|---|
| 16-core host, 10 SQL VMs (4 vCPU each) | 40 core licences per-VM ($570K Ent) | 16 core licences per-host ($228K Ent) | $342K (60 %) |
| 32-core host, 20 SQL VMs (4 vCPU each) | 80 core licences per-VM ($1.14M Ent) | 32 core licences per-host ($456K Ent) | $684K (60 %) |
| 3-host cluster (48 cores), 30 SQL VMs | 120 core licences ($1.71M Ent) | 48 core licences ($684K Ent) | $1.03M (60 %) |
| Key point | Unlimited virtualisation means new SQL VMs on licensed hosts require zero incremental licences — eliminating true-up exposure and provisioning delays | ||
"Unlimited virtualisation with Enterprise + SA is the single most powerful SQL Server licensing optimisation. Consolidate SQL workloads onto fewer, fully licensed hosts and run any number of instances. The ROI compounds as VM density increases — every additional VM on a licensed host is effectively free."
Benefit 4 — Passive Failover Rights
SA provides the right to operate one passive secondary SQL Server instance for high availability and disaster recovery — at no additional licence cost.
What "Passive" Means
The secondary instance can receive data through log shipping, database mirroring, or Always On Availability Groups, and can be used for brief failover testing and maintenance patching. It cannot serve read queries, run reports, or process any production workload during normal operation. In Always On, the secondary must have ALLOW_CONNECTIONS = NO to qualify as passive. Setting it to READ_ONLY or ALL makes it active — requiring its own licence. This single benefit effectively doubles the value of your licence: two servers for the price of one, in HA configuration.
Azure as DR Site
SA extends passive failover rights to Azure: you can run a passive SQL Server VM in Azure as your DR replica without additional licensing. The Azure VM uses AHB for the compute cost (paying only base Linux rate), and the passive failover right covers the SQL licence. This makes Azure DR significantly cheaper than maintaining a second physical data centre. For organisations with SA-covered SQL Enterprise: the combination of AHB + passive failover in Azure can provide enterprise-grade DR for under $5K/year per instance in Azure infrastructure costs alone — compared to $50K+ for a physical DR site with separate licences.
Benefit 5 — Azure Hybrid Benefit (AHB)
AHB is SA's highest-value benefit for organisations adopting Azure. Each SA-covered SQL Server core licence offsets Azure SQL pricing by removing the SQL licence component from the hourly rate.
| Azure Resource | Enterprise Core → Azure Mapping | PAYG Rate | AHB Rate | Savings |
|---|---|---|---|---|
| SQL Server on Azure VM (D8s_v5) | 8 Enterprise cores → 8 vCPUs | $2.50/hr | $0.77/hr | 69 % |
| Azure SQL Managed Instance (8 vCore BC) | 8 Enterprise cores → 8 vCores | $5.40/hr | $2.16/hr | 60 % |
| Azure SQL Database (8 vCore GP) | 2 Enterprise cores → 8 vCores GP | $1.84/hr | $0.92/hr | 50 % |
| Annual impact (10 D8s_v5 VMs) | $219K/yr | $67K/yr | $152K/yr saved | |
AHB Activation — The Most Commonly Missed Optimisation
AHB is a billing toggle — you declare it when creating or modifying an Azure resource. There is no migration, no configuration change, no downtime. Yet in our advisory engagements, we consistently find that 30–50 % of eligible Azure SQL resources are running at full PAYG rates because the AHB toggle was not activated. The fix takes seconds per resource: go to the Azure portal → select the SQL resource → change the licence type to "Azure Hybrid Benefit". For organisations with 50+ Azure SQL resources, this single action can save $200K–$500K annually. SAM teams should audit Azure billing monthly for SQL resources not using AHB.
Benefit 6 — Per-VM Licensing (SQL 2022+)
Starting with SQL Server 2022, SA is required for per-VM licensing in virtualised environments. This change makes SA functionally mandatory for any organisation running SQL VMs without licensing the entire physical host.
What Changed
Previously, you could licence individual SQL VMs with perpetual licences (no SA) as long as you observed the 90-day reassignment rule. SQL Server 2022 changed this: per-VM licensing now requires active SA on every licence assigned to a VM. If SA lapses, those per-VM licences become invalid for virtual deployment. You must either: (a) renew SA, (b) licence the entire physical host, or (c) migrate to a subscription model (CSP or Azure). This change, combined with licence mobility requirements, means SA is now a baseline requirement — not an optional add-on — for virtualised SQL Server 2022+ deployments.
Benefit 7 — Step-Up Rights and Additional Benefits
Step-Up from Standard to Enterprise
SA enables step-up licensing: upgrade from Standard Edition to Enterprise by paying only the price difference (plus SA on the difference), rather than purchasing a full Enterprise licence. For a 16-core server: full Enterprise purchase is $228K; step-up from Standard (if already owned) is approximately $165K — saving $63K per server. This is valuable when workloads grow to require Enterprise features (Always On AGs, unlimited virtualisation, data compression). Plan step-ups at EA renewal for maximum negotiation leverage.
Planning Services and Training
SA includes Planning Services days (Microsoft or partner consultants help plan deployments/migrations), training vouchers for Microsoft courses, and support incidents for critical issues. These are frequently unused — but their value is real. Use Planning Services for SQL Server upgrade roadmaps or cloud migration assessments. Training vouchers keep DBAs current on licensing changes and new features. Support incidents provide direct Microsoft engineering assistance for critical SQL issues that would otherwise require expensive Premier/Unified Support.
SA Renewal Strategy — Maintain or Lapse?
When to Renew
Renew SA when any of the following apply: (1) you run SQL Server in virtualised environments (SA is mandatory for per-VM licensing and licence mobility), (2) you use or plan to use Azure Hybrid Benefit, (3) you anticipate upgrading to a newer SQL Server version within the SA period, (4) you rely on passive failover rights for DR, or (5) your SQL estate exceeds 50 cores (the cumulative SA benefits almost certainly exceed the cost). For most enterprises, maintaining SA is the default recommendation.
When Lapsing May Be Justified
Lapsing SA may be justified when: (1) SQL Server runs on physical servers only (no virtualisation, no mobility needed), (2) you do not plan to upgrade versions and are satisfied with the current release, (3) you have no Azure or cloud deployment plans, and (4) you do not use passive failover (or are willing to licence DR servers separately). These conditions are rare in modern enterprises. Before lapsing, calculate the cost of re-acquiring SA later (requires repurchasing the underlying licence at current list price) — this "re-entry penalty" often exceeds several years of continued SA payments.
✅ SAM Recommendations — Maximising SQL Server SA Benefits
- Audit AHB activation monthly: Check every Azure SQL resource for AHB status. Unactivated AHB is the single most common waste in SQL Server licensing — fixing it saves 40–69 % per resource immediately
- Exercise passive failover rights: If you have SA and no DR secondary, you are leaving a free licence on the table. Deploy a passive standby — on-premises or in Azure — covered by your existing SA entitlement
- Consolidate onto Enterprise + SA hosts: For virtualised environments with 4+ SQL VMs per host, per-host Enterprise + SA with unlimited virtualisation is almost always cheaper and simpler than per-VM licensing. Model both approaches at each EA renewal
- Upgrade before SA expires: If SA is lapsing and a newer SQL version is available, upgrade all instances before expiry to lock in the latest version as your perpetual entitlement
- Use step-up rights proactively: If workloads are approaching Enterprise feature requirements, step-up from Standard during the current SA period rather than purchasing full Enterprise licences later
- Claim Planning Services: SA includes consulting days from Microsoft or partners — use them for SQL Server migration planning, cloud assessment, or licensing optimisation. These are prepaid services that expire if unused
- Document SA coverage dates meticulously: SA expiry dates determine eligibility for every benefit. Maintain a register linking each SQL licence to its SA start/end dates, and set alerts 6 months before expiry for renewal decisions
- Calculate SA ROI annually: Quantify the value of each benefit you used during the year (upgrade savings, AHB savings, mobility value, failover savings) versus SA cost. If ROI exceeds 2×, renewal is clear. Share this analysis with finance to justify continued SA investment