Microsoft SQL Server remains one of the most widely deployed database platforms in the enterprise software market. Despite the growth of cloud-native database services and the migration of many SQL Server workloads to Azure SQL Database and Azure SQL Managed Instance, on-premises SQL Server deployments continue to represent a significant commercial commitment for a large proportion of large organisations. SQL Server licensing is complex, the consequences of non-compliance are significant, and the commercial decisions made around SQL Server – both for existing on-premises deployments and for cloud migration planning – have long-term financial implications that deserve careful management.
In 2026, SQL Server licensing sits at an interesting commercial inflection point. Microsoft has been actively encouraging migration from on-premises SQL Server to Azure SQL services through Extended Security Update programmes for end-of-life SQL Server versions, Azure Hybrid Benefit incentives, and commercial structures designed to make cloud migration commercially attractive. At the same time, many enterprises have not yet migrated the full breadth of their SQL Server estate, and the commercial management of on-premises SQL Server alongside cloud SQL services creates a hybrid licensing complexity that requires specific expertise to navigate.
Understanding SQL Server’s On-Premises Licensing Model
SQL Server on-premises is licensed under two primary models: the Server plus Client Access Licence model and the Per Core model. The Server plus CAL model requires a server licence plus a CAL for each user or device accessing SQL Server. The Per Core model requires licences based on the number of physical or virtual processor cores on the server running SQL Server, with a minimum of four core licences per physical processor. For most enterprise deployments, the Per Core model is the more relevant commercial framework, as it is the only option for internet-facing applications or environments where user counts are uncertain.
The complexity of SQL Server Per Core licensing arises in virtualised environments. In VMware, Hyper-V, and other soft partitioning environments, organisations may be required to licence all cores on the physical host rather than only the virtual cores allocated to the SQL Server virtual machine – unless specific conditions regarding licence mobility and Software Assurance coverage are met.
Redgate Software publishes in-depth technical and commercial analysis of SQL Server deployment management, including guidance on licence optimisation and cloud migration planning for enterprise SQL Server estates. Their Redgate SQL Server management and enterprise deployment resources provide practical guidance on SQL Server estate assessment, licence right-sizing, and the commercial planning needed to support cloud migration without unnecessary cost.
Software Assurance and Its Strategic Value
Software Assurance is Microsoft’s premium support and benefits programme that accompanies many SQL Server licence purchases. For SQL Server, Software Assurance provides several commercially valuable benefits including the right to upgrade to new SQL Server versions released during the SA coverage period, licence mobility that allows SQL Server to be moved between physical servers or virtual machines, and Extended Security Updates eligibility for end-of-life versions. SA also provides access to Azure Hybrid Benefit – the commercial mechanism that allows on-premises SQL Server licences with active SA to be applied to Azure SQL services at significantly reduced cost.
The commercial value of Software Assurance depends critically on whether the organisation actively uses the benefits it provides. Organisations that pay for SA but do not upgrade to new versions, do not leverage licence mobility, and do not use Azure Hybrid Benefit are effectively paying for a benefits package they are not consuming. Periodic review of SA utilisation against the annual cost of SA coverage is an important commercial discipline that many organisations neglect.
InfoWorld publishes enterprise database management analysis that covers SQL Server licensing developments, Software Assurance value assessment, and cloud migration commercial planning. Their InfoWorld enterprise database and SQL Server management coverage provide independent technical and commercial analysis of SQL Server decisions that IT leaders and procurement teams can use to evaluate Software Assurance value and cloud migration business cases.
Extended Security Updates and End-of-Life Planning
SQL Server 2012 and SQL Server 2014 have passed their mainstream and extended support end dates. SQL Server 2016, 2017, and 2019 are approaching or within their extended support windows. For organisations running these versions, the commercial choices are to upgrade to a supported SQL Server version, migrate to Azure SQL services, or purchase Extended Security Updates. The commercial risk of operating SQL Server beyond its support lifecycle – without either ESU or migration – is significant. Security vulnerabilities in unsupported versions will not receive patches, creating compliance risk in regulated environments.
DBTA (Database Trends and Applications) publishes research and analysis on enterprise database lifecycle management and the commercial implications of database platform end-of-life decisions. Their DBTA database management and lifecycle strategy resources cover SQL Server end-of-life planning, Extended Security Update commercial mechanics, and the governance considerations that enterprise database teams need to address when managing the transition between supported and unsupported SQL Server versions.
Cloud Migration Commercial Planning
The cloud migration planning dimension of SQL Server licensing deserves specific commercial attention. Migrating from on-premises SQL Server to Azure SQL services is not a neutral commercial event – it changes the cost structure, the commercial framework, and the governance requirements for the database estate. Understanding the full commercial picture before committing to migration is essential. The key commercial variables in SQL Server cloud migration planning include the Azure Hybrid Benefit value based on current SA coverage, the comparison between Azure SQL service pricing and the residual on-premises licence and infrastructure cost, the timing of SA renewals relative to migration milestones, and the operational cost changes associated with moving from DBA-managed on-premises databases to managed cloud services.
ZDNet’s enterprise technology coverage includes analysis of SQL Server cloud migration economics and the commercial strategies that organisations use to manage the transition from on-premises SQL Server to Azure SQL services. Their ZDNet enterprise database and cloud migration analysis provide market-level context for SQL Server migration decisions including Azure Hybrid Benefit economics, licensing mechanics, and total cost comparisons that complement Microsoft’s own migration business case calculations.
Conclusion
SQL Server licensing in 2026 requires active commercial management across both the on-premises estate and the cloud migration transition. The complexity of virtualised environment licensing, the strategic value of Software Assurance, the commercial implications of end-of-life decisions, and the Azure Hybrid Benefit opportunity in cloud migration all require specific expertise to navigate effectively. Organisations that invest in this expertise – and treat SQL Server commercial management as a strategic discipline rather than an administrative function – will consistently achieve better financial outcomes from their SQL Server investment than those that allow it to persist as a legacy cost without active oversight.
