SQL Server
Microsoft's relational database engine. Licensed per physical core (4-core minimum per physical processor or per VM) or under the Server + CAL model for smaller deployments.
Also known as: MS SQL, SQL Server Standard, SQL Server Enterprise
Last reviewed by MSLicenseHub Licensing Desk on 2026-11-12.
At a glance
- Licensing model
- Per-core (4-core minimum) OR Server + CAL
- Related entities
- Software Assurance · Always On AG · Passive secondary rights · Enterprise edition · Standard edition
Key licensing rules
- Per-core licensing: license every physical core of the server (minimum 4 per processor), or each virtual machine by its virtual cores (minimum 4 per VM).
- The Server + CAL model exists only for Standard edition; Enterprise edition is licensed per core.
- Since SQL Server 2022, licensing individual VMs by virtual core requires active Software Assurance or subscription licences.
- Developer edition is free but only for development and testing; Express is free for small production databases within its resource limits.
- Free passive failover replicas are a Software Assurance (or subscription) benefit, not a right of the licence alone.
Common mistakes and how to avoid them
Any production use, including reporting for real users, needs Standard or Enterprise licences.
Enterprise is per-core only; Server + CAL applies to Standard.
Users reaching SQL Server through an application or pooling layer still count under the CAL model.
Confirm active SA or subscription before relying on passive secondary rights.
Before you request a quote, gather
- Edition features required (Standard vs Enterprise)
- Physical cores, or virtual cores per VM
- Number of users/devices if Server + CAL is considered
- High-availability and disaster-recovery replicas
- Software Assurance, subscription or Azure Hybrid Benefit plans
Compare options
In-depth articles
An architectural and procurement breakdown of SQL Server 2022 editions: compare Standard, Enterprise, Express,…
Explore this detailed case study on how a global mid-size firm navigated the complexities of SQL Server 2022 v…
Navigating SQL Server licensing is critical for sysadmins. This guide compares Core-based vs. Server+CAL model…
The Azure Hybrid Benefit is one of Microsoft’s most powerful cost-saving mechanisms, allowing you to leverage …
Frequently asked questions
Can I use SQL Server Developer Edition in production?
No. Developer Edition is feature-equivalent to Enterprise but the license restricts use to development, testing and demonstration — never production workloads. The moment a real customer or business process depends on the data, you are out of compliance.
Microsoft enforces this in audits, and converting a Developer install to production after the fact is not a defense. If you need Enterprise features in production, license Enterprise. If Standard is enough, license Standard. For free production use with hard limits, SQL Server Express is the only legitimate path.
🔄 Updated 2026-11-11
As of late 2026, the licensing terms for SQL Server Developer Edition remain unchanged. The software continues to be feature-equivalent to the Enterprise edition, but its usage remains strictly limited to development, testing, and demonstration environments.
There is no path to "convert" or license a Developer Edition installation for production use. If a workload transitions from a development phase to a production state—where it serves real business processes or external users—the environment must be migrated to a production-licensed version of SQL Server. Organizations failing to do so risk non-compliance during a Microsoft audit.
Practical Recommendations:
- For Production Environments: If you require the features found in Enterprise or Standard editions, you must acquire a Retail or Volume License.
- For Free Production Use: If you seek a no-cost option for production, SQL Server Express is the only supported choice, provided your workload fits within its technical constraints (such as maximum compute and database size limits).
Always review the current Microsoft Product Terms to ensure your deployment aligns with your specific usage and licensing requirements.
Frequently asked questions
Can I use SQL Server Developer Edition in production?
No. Per Microsoft licensing terms, SQL Server Developer Edition is strictly for non-production development, testing, and demonstration purposes only. Production use is a violation of the license agreement.
What is a free alternative to Developer Edition for production?
If you require a free version of SQL Server for production workloads, you must use SQL Server Express, which includes defined hardware and database size limitations.
Sources
When is Software Assurance worth paying for?
Software Assurance (SA) adds roughly 25–29% per year on top of a perpetual Volume License. It is worth it when you actually use the benefits:
- Version upgrades — the biggest benefit. Without SA, every major upgrade is a fresh purchase.
- License Mobility — needed to run server workloads (SQL Server, SharePoint) on Azure or AWS using your existing license.
- Azure Hybrid Benefit for Windows Server and SQL — saves roughly 40% on Azure VM and SQL DB pricing.
- Training vouchers, planning services, 24/7 problem-resolution support.
SA is rarely worth it for desktop apps you do not plan to upgrade. It almost always pays for itself on Windows Server, SQL Server and Exchange Server in 3 years.
🔄 Updated 2026-11-10
Updated 2026-11-10: As of late 2026, the strategic value of Software Assurance (SA) continues to center on total cost of ownership (TCO) for hybrid environments. While cloud-native services have evolved, SA remains the essential vehicle for the Azure Hybrid Benefit, which continues to be a primary driver for cost efficiency when deploying Windows Server and SQL Server workloads in Azure. Organizations should evaluate SA strictly based on their three-year infrastructure roadmap rather than generic bundles. If your strategy involves migrating existing on-premises perpetual workloads to the cloud, the potential savings from SA typically outweigh the annual maintenance premiums. Conversely, for static, localized environments where no hardware refresh or version upgrade is scheduled within the next 36 months, the return on investment for SA is significantly diminished.
Frequently asked questions
Is Software Assurance still relevant in a cloud-first era?
Software Assurance remains the primary mechanism for accessing new version rights, the Azure Hybrid Benefit, and specific hybrid cloud deployment flexibilities. It is most valuable for organizations with standardized server infrastructures and those actively migrating to or operating within a hybrid cloud environment.
Sources
What is Azure Hybrid Benefit?
Azure Hybrid Benefit (AHB) lets you reuse Windows Server and SQL Server licenses with active Software Assurance on Azure VMs and Azure SQL — without paying for the Windows or SQL component a second time. The Azure VM price drops to the "compute only" rate, saving roughly 40% versus pay-as-you-go.
To use AHB, the license needs an active SA contract or an active subscription, and you toggle the Hybrid Benefit flag on the VM or SQL resource in the Azure portal. Microsoft permits dual-use for 180 days during a cloud migration, so you can keep the on-prem workload running while you cut over.
🔄 Updated 2026-11-10
Azure Hybrid Benefit (AHB) remains a vital strategy for organizations looking to optimize their cloud expenditures as of November 2026. The core value proposition—reducing Azure Virtual Machines and Azure SQL costs by utilizing existing on-premises Windows Server and SQL Server licenses—is unchanged.
Key Considerations for 2026:
- License Compliance: Ensure your Software Assurance (SA) or qualifying subscription coverage is current. AHB benefits are tethered to the validity of these agreements.
- Azure Arc Integration: Microsoft has increasingly streamlined the management of AHB through Azure Arc-enabled servers. This allows for more granular visibility into your hybrid estate and helps ensure that your entitlements are accurately applied to eligible resources.
- Reporting and Governance: Utilize the Azure Hybrid Benefit reporting tools available in the Azure portal to track usage and avoid potential over-allocation or under-utilization of your license pool.
Practical Recommendation: Organizations should conduct a quarterly audit of their on-premises licensing versus their Azure deployment. As your cloud footprint scales, leverage the Azure portal to verify that the AHB flag is correctly enabled for all eligible workloads to prevent unnecessary pay-as-you-go charges. If you are planning a transition, maintain strict documentation of your dual-use migration period to remain within compliance guidelines.
Frequently asked questions
What is Azure Hybrid Benefit?
Azure Hybrid Benefit applies to Windows Server and SQL Server licenses covered by active Software Assurance or qualifying subscriptions. It allows you to pay only the base compute rate for Azure VMs and Azure SQL, significantly reducing your total cost of ownership.
How do I activate Azure Hybrid Benefit?
You can manage your AHB entitlements directly through the Azure portal by toggling the benefit on your specific resources. For large-scale environments, you can also manage these benefits via the Azure Cost Management + Billing blade.
Sources
What is Azure Arc and do I need a license for it?
Azure Arc extends Azure's management plane to servers, Kubernetes clusters and SQL databases running outside Azure — on-prem, in AWS, or at the edge. Once connected, those resources appear in the Azure portal and can be managed with Azure Policy, Update Manager, Defender for Cloud and Monitor.
The Arc connection itself is free. Individual services you turn on (Defender for Servers, Update Manager, SQL Managed Instance enabled by Arc, Azure Monitor) are billed per their normal Azure rates. There is no separate "Arc license".
🔄 Updated 2026-11-13
Updated 2026-11-13: As of November 2026, the licensing model for Azure Arc remains consistent with its original architecture. Azure Arc acts as a connectivity bridge for resource management and governance, and there is no charge for the Arc connection itself. Organizations should note that while the Arc agent is free, activating management capabilities such as Defender for Cloud, Azure Monitor, or specific SQL extensions will trigger billing according to the standard consumption rates for those specific services. When planning your multi-cloud or hybrid infrastructure strategy, ensure your budget accounts for the usage-based fees of the enabled services rather than any upfront licensing for the management platform itself.
Frequently asked questions
Is there a specific license for Azure Arc?
Azure Arc itself is a free management bridge. You do not purchase an 'Azure Arc license.' However, you are billed for the specific Azure services (such as Microsoft Defender for Cloud or Azure Monitor) that you enable on your connected resources based on their standard consumption rates.
Sources
What is a CAL?
A Client Access License (CAL) authorizes a user or device to access a Microsoft server product such as Windows Server, Exchange or SharePoint. The server itself needs its own server license; the CALs cover who connects to it. Without enough CALs, you are technically out of compliance even if every server license is paid for.
CALs come in two flavors. A User CAL follows a person across every device they use, which is the right choice for staff with a laptop, a phone, and a desktop. A Device CAL is tied to a specific machine and covers anyone who logs into it — better for shift workers who share kiosks or shop-floor PCs.
🔄 Updated 2026-11-09
Updated 2026-11-09: The fundamental requirement for a Client Access License (CAL) remains a cornerstone of Microsoft's on-premises server licensing model. As of late 2026, while many organizations have migrated workloads to cloud-native services, the need for CALs persists for any user or device connecting to traditional Windows Server, Exchange, or SharePoint deployments. Compliance remains critical; ensure your procurement strategy aligns with your workforce mobility and device usage patterns to avoid gaps in coverage during audits.
Frequently asked questions
Do I still need CALs for server workloads in the cloud?
Yes. If you are accessing services hosted on a Windows Server instance, you must ensure you have the appropriate CAL coverage for users or devices, regardless of whether the server is physical, virtual, or hosted in an IaaS environment.
Sources
User CAL vs Device CAL — which one is cheaper?
The math is simple. Count how many users and how many devices will access the server. Whichever number is smaller is the SKU you want.
If 30 staff each have a laptop, a phone and a desktop (90 devices, 30 users), User CALs win — you buy 30 instead of 90. If 20 shift workers share 5 shop-floor terminals around the clock (5 devices, 20 users), Device CALs win — you buy 5 instead of 20. The CAL type is set per server role, so the Exchange Server and the Windows Server in the same rack can use different CAL types.
🔄 Updated 2026-11-09
The fundamental strategy for managing User CAL vs Device CAL costs remains focused on your organization's unique access patterns. While cloud-based subscriptions continue to evolve, traditional on-premises server access still relies on these core licensing models. There have been no structural changes to how these licenses function; the selection process remains a straightforward audit of your internal infrastructure.
For today's deployments, consider the following best practices:
- Assess Remote Work Patterns: As hybrid work remains standard, the ratio of devices per user has often increased, making User CALs the common choice for office staff.
- Review Lifecycle Costs: Remember that CALs are generally perpetual licenses (if acquired via Retail or Volume Licensing). Always consult your Microsoft representative or authorized partner to ensure your current volume agreement (e.g., Enterprise Agreement or CSP) provides the most favorable pricing for your specific volume.
- Maintain Compliance: CALs are non-transferable between users or devices in most scenarios. Ensure your internal tracking reflects your chosen model, as Microsoft licensing audits require proof of entitlement based on your initial deployment selection.
Always acquire licenses through authorized Microsoft partners or the Microsoft Volume Licensing Service Center to ensure full support and compliant entitlement records. Avoid aftermarket sources that lack verified chain-of-custody.
Frequently asked questions
Can I mix User CALs and Device CALs for the same server?
No, Client Access Licenses (CALs) are not interchangeable. You must choose one type per server environment; mixing User and Device CALs for the same server software is generally not permitted under standard licensing terms.
How do I know which CAL type is right for my organization?
User CALs are typically more cost-effective for employees who use multiple devices (laptop, mobile, desktop) to access services. Device CALs are more economical for environments with fewer machines than users, such as kiosks, shift-work stations, or clinical terminals.
Sources
Glossary terms
Related pages and official sources
Binding terms: Microsoft Product Terms · SQL Server 2025 editions and features · Microsoft product lifecycle. This hub is general guidance, not a substitute for your agreement.