SQL Server 2016 licensing depends on the edition, how the server is deployed, and whether access is licensed by cores or by users and devices. Its Extended Support ended on July 14, 2026, so organizations should assess both their existing license rights and their security and migration plans. Extended Security Updates (ESUs) are a limited, temporary security bridge—not a return to normal support.
SQL Server 2016 licensing at a glance
SQL Server 2016 had two principal commercial licensing models: Per Core and Server + CAL. Standard was available under either model. New Enterprise licenses were Per Core; some customers with qualifying legacy Enterprise Server + CAL licenses and active Software Assurance (SA) may retain those rights, subject to a 20-core limit. The customer’s agreement, purchase records, and applicable Microsoft Product Terms determine the rights for a specific deployment.
| Edition | Licensing position | Typical use |
|---|---|---|
| Enterprise | Per Core for new licensing. Qualifying legacy Server + CAL rights may remain with active SA, subject to a 20-core limit and applicable terms. | Advanced or mission-critical workloads |
| Standard | Per Core or Server + CAL | General business databases and reporting |
| Web | Primarily through the Services Provider License Agreement (SPLA) provider channel | Web hosting |
| Developer | Free for development and testing; not licensed for production | Development, CI, and non-production testing |
| Express | Free, with technical limits | Learning, small applications, or lightweight deployments |
| Evaluation | Time-limited evaluation; not a production licensing solution | Temporary evaluation |
Microsoft’s SQL Server 2016 edition overview describes edition capabilities. The SQL Server 2016 licensing datasheet summarizes the historical licensing models. Neither installation media nor a product key, by itself, proves that an organization has the necessary usage rights.
Choose between Per Core and Server + CAL
Per Core
Per Core licensing covers SQL Server by licensing the relevant physical or virtual cores. It does not require SQL Server CALs. It is commonly the model to evaluate when users or devices are difficult to count, when a workload is public-facing, or when access is mediated by an application that serves a large or changing population.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
Server + CAL
Under Server + CAL, each server or virtual machine running SQL Server needs the appropriate server license, and each user or device accessing it needs a SQL Server Client Access License (CAL). A User CAL follows one person across devices; a Device CAL covers one device used by multiple people. A CAL must generally be the same version as, or newer than, the SQL Server version it accesses. A CAL can generally access multiple appropriately licensed SQL Server instances, subject to the agreement and applicable terms.
This model can suit a controlled environment with a known, stable population. A web application, connection pool, reporting front end, or middleware layer does not automatically remove the obligation to license the underlying users or devices. Anonymous, customer, partner, or other external access can make counting impractical; Per Core is usually the model to analyze in those cases.
Count cores on a physical server
For physical Per Core licensing, determine the physical cores in the relevant physical operating-system environment and apply the minimum of four core licenses per physical processor. License all relevant physical cores when licensing the physical server; do not reduce the count just because SQL Server is configured to use fewer cores unless the applicable rules recognize that configuration.
- Record each processor and its physical-core count.
- For each processor, use at least four core licenses, even if it has fewer than four physical cores.
- Add the applicable counts across processors and license the resulting core total for the SQL Server edition and deployment.
- Check the agreement and Product Terms for partitioning, virtualization, and any Software Assurance or subscription rights relevant to the planned use.
| Physical configuration | Core licenses under the stated minimum |
|---|---|
| One processor with four physical cores | 4 |
| Two processors with eight physical cores each | 16 |
| Two processors with two physical cores each | 8 (four per processor) |
| One 24-core physical host running SQL Server Standard in its physical OSE | Ordinarily 24 Standard core licenses, subject to the applicable agreement and terms |
Processor affinity, hardware partitioning, and virtualization can affect the analysis. Document the hardware and configuration rather than relying on current CPU utilization or an assumed count.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallLicense SQL Server in virtual machines
License each VM individually
For Per Core licensing of an individual VM, license the virtual cores assigned to it, subject to a minimum of four core licenses per VM. A two-vCPU VM therefore generally requires four core licenses; a six-vCPU VM generally requires six. Hyper-threading and the way virtual cores map to hardware can affect the count, so confirm the treatment under the applicable terms.
Under Standard Server + CAL, the VM instead needs a Standard server license and the required CALs for its accessing users or devices. The SQL Server 2016 Virtualization Licensing Guide explains the historical virtualization models.
License the host for high VM density
Qualifying Enterprise core licensing with active SA can provide unlimited virtualization rights on the licensed server, subject to the applicable rules. This can be worth evaluating when a host runs many SQL Server VMs or VM placement changes frequently. Do not assume the same right applies to Standard, or that Enterprise licensing alone is enough: eligibility and SA status matter.
Compare the cost and administrative effort of licensing each VM—including each VM’s four-core minimum—with licensing all physical cores under qualifying Enterprise and SA rights. The result depends on core counts, VM allocations, contract terms, and existing entitlements; there is no universal break-even point.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Understand legacy Enterprise Server + CAL rights
New Enterprise licenses were not offered under Server + CAL. A customer with qualifying Enterprise Server + CAL licenses and active SA may have retained rights to upgrades, including SQL Server 2016, but the legacy deployment is limited to 20 or fewer cores and still requires appropriate CALs. This is distinct from a new Enterprise Per Core purchase and from Standard Server + CAL. Verify the original licenses, SA coverage, upgrade history, and applicable terms before relying on the exception.
What Software Assurance can change
SA is not simply a maintenance fee: depending on the license, agreement, and eligibility, it can affect access to newer versions, license mobility, individual-VM licensing, maximum virtualization, Azure Hybrid Benefit, and certain failover or disaster-recovery rights. It also matters to legacy Enterprise Server + CAL upgrade rights. No one of these benefits should be assumed to apply automatically to every SQL Server 2016 license. Check the customer’s agreement and the Microsoft SQL Server Product Terms.
License mobility and reassignment
License Mobility through SA may allow qualifying licenses to move in certain server-farm or third-party-hosting scenarios. It is distinct from the ordinary reassignment restriction commonly described as preventing reassignment between servers more than once every 90 days, and it is not the same as Azure Hybrid Benefit. Moving a VM between hosts does not, by itself, establish that its SQL Server license can move with it. Confirm that the license has the relevant mobility right and that the hosting arrangement meets its conditions.
Plan failover, high availability, and disaster recovery
Do not assume every passive replica or recovery server is free. Rights can depend on edition, license model, SA status, the server’s purpose, and the applicable Product Terms. This matters for failover clustering, Always On availability groups, log shipping, warm standbys, cloud recovery environments, and read-only reporting replicas.
- Document which nodes are active and passive and what each one does.
- Record whether a secondary is used for reporting, backups, read-only queries, testing, or other work.
- Check the relevant agreement and Product Terms for the exact failover or disaster-recovery right before treating a server as unlicensed.
Distinguish Azure and hosted options
| Deployment | What to assess |
|---|---|
| SQL Server on an Azure VM | License-included pricing and eligible bring-your-own-license rights are different commercial models. Azure Hybrid Benefit may apply to qualifying SQL Server core licenses with active SA or a qualifying subscription. |
| Azure SQL Managed Instance or Azure SQL Database | These are Azure services, not ordinary SQL Server 2016 installations. Their service terms and compatibility differ from licensing a SQL Server VM. |
| Third-party hoster | Check the hoster’s licensing arrangement, including whether it operates under SPLA, and whether the customer’s own license has a qualifying mobility right. |
| Azure Hybrid Benefit | This is not automatic transfer of any SQL Server license to any cloud service. Eligibility depends on the license, SA or subscription, service, and deployment terms. |
Microsoft states that one SQL Server Enterprise core license with SA can provide coverage for up to four Azure vCores in relevant scenarios, subject to the applicable terms. Check the Azure Hybrid Benefit FAQ for the scenario rather than applying that ratio to every service or configuration. The Microsoft SQL Server licensing document library is an entry point for licensing material.
Account for SQL Server 2016’s support status
SQL Server 2016 is version 13.x. Microsoft lists Mainstream Support as ending July 13, 2021, and Extended Support as ending July 14, 2026. Licensing validity and support status are separate: an organization may still hold valid usage rights while running a product outside regular support. See Microsoft’s SQL Server 2016 lifecycle page.
Microsoft’s scheduled ESU periods run from July 15, 2026 through July 13, 2027; July 14, 2027 through July 18, 2028; and July 19, 2028 through July 17, 2029. ESUs cover qualifying security updates only. They do not add features or restore ordinary troubleshooting and product support. See the SQL Server Extended Security Updates FAQ and SQL Server-specific ESU FAQ.
Upgrade or migrate
Assess a move to a supported SQL Server release or an Azure database option. Test application compatibility, operating-system and hardware requirements, third-party support, and licensing before choosing an upgrade path. Azure SQL Managed Instance may suit some legacy workloads; Azure SQL Database is a different service model and may require more application changes.
Use ESUs only as a bridge
ESUs can help qualifying organizations manage a staged migration, but they are not a long-term support plan. Confirm eligibility and how ESUs are obtained for the specific deployment; do not equate an ESU with a current SQL Server license or normal support.
Compare common deployment scenarios
| Scenario | Licensing approach to evaluate | Key check |
|---|---|---|
| Small internal Standard database with a known employee population | Standard Server + CAL versus Standard Per Core | Compare the server license and required User or Device CALs with the core count and existing entitlements. |
| Public website with anonymous users and pooled connections | Per Core is generally the model to analyze | Application-layer multiplexing does not automatically remove access licensing obligations. |
| Two-vCPU Standard VM | Individual-VM Per Core or Standard Server + CAL | Per Core generally has a four-core minimum per VM; Server + CAL requires CALs for access. |
| Many SQL Server VMs on a changing, consolidated host | Individual VM licensing versus qualifying Enterprise core licensing with SA | Verify maximum-virtualization eligibility and compare the actual VM and host counts. |
| Failover or disaster-recovery environment | Assess rights for each active and passive node | Document use and verify the applicable failover terms; do not assume a passive node is free. |
| Development lab | Developer for development and testing, or Express if its limits fit | Neither is a general production substitute. |
Audit the deployment before buying or changing licenses
- Record SQL Server edition, version, and every installed instance.
- Identify the licensing model and gather purchase records, agreement terms, and entitlement documentation.
- For physical deployments, record processors, physical cores, operating-system environments, and any partitioning.
- For virtual deployments, record each VM’s assigned vCPUs, host, cluster, and migration or resizing practices.
- For Server + CAL, count users and devices, identify CAL type and version, and review external and multiplexed access.
- Record SA or qualifying subscription status and the dates it was active.
- Document active, passive, reporting, backup, and recovery uses for every replica or secondary server.
- For hosted and cloud deployments, identify the service, pricing model, hoster terms, and any claimed mobility or Azure Hybrid Benefit.
- Record ESU eligibility and plans for migration or upgrade.
For complex estates, legacy entitlements, third-party hosting, or ambiguous failover rights, obtain a written interpretation from Microsoft or an authorized licensing partner. The historical datasheet is useful guidance, but it is not a substitute for the customer’s contract and applicable Product Terms.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
