We’ve put together this FAQ to help you navigate through the SQL Server 2019 licensing options
and to answer some of the most common questions related to SQL licensing in different deployment scenarios.
For information about SQL Server 2022 see the
MS SQL Server 2022 Licensing FAQ.
What editions are available with SQL Server 2019?
What licensing options are available for SQL Server 2019?
Howto license a SQL server under the Per Core licensing model?
How to license a SQL server using the Server + CAL licensing model?
How to license a container running SQL Server software?
SQL Server is offered in the following editions:
For more information see the SQL Server 2019 editions datasheet and the Editions and supported features of SQL Server 2019 web page.
SQL Server Enterprise Edition can be licensed only under the Per Core model.
SQL Server Standard Edition can be licensed either under the Per Core model
or under the Server + CAL model.
For SQL Server 2019 Big Data Clusters, customers can purchase SQL Server Enterprise
or Standard Per Core licenses for master instance and Big Data
Node cores for Big Data Nodes or worker nodes.
Core licenses are sold in packs of two. That is, one
SKU, called 2 core pack, contains two core licenses.
SQL Server Licenses are platform agnostic and permit deployment and use on Windows or Linux systems.
Software Assurance (SA) is an optional software support offering available through the Volume Licensing programs. SA is purchased together with the base license and must be renewed on a periodic basis to remain active.
SA provides many benefits, including:
For more information on these and other SA benefits, see the Software Assurance overview web page.
Under the Per Core licensing model, each server running SQL Server or any of its components must be assigned an appropriate number of SQL Server 2019 core licenses. The number of required core licenses depends on whether customers are licensing a physical server or individual virtual operating system environments (OSEs). OSE is defined as an operating system (OS) instance installed either on a physical server or on a virtual machine.
To license SQL Server Enterprise or Standard running in a physical OSE, all physical cores on the server must be licensed with the respective SQL Server 2019 licenses. A minimum of four core licenses is required for each physical processor on the server.
For example:
There are two options for licensing SQL Server in a virtualized environment under the Per Core licensing model:
In order to license an individual VM (virtual OSE) for SQL Server Enterprise or Standard, all virtual cores (v-cores, virtual processors, virtual CPUs) allocated to the VM must be licensed with the corresponding SQL Server 2019 licenses, subject to a minimum four-core license per VM. For example:
If all physical cores on a server are licensed with SQL Server Enterprise Edition, customers can run SQL Server software in a number of OSEs (physical and/or virtual) equal to the number of core licenses assigned to the server. In such configuration there are no restrictions on the number of vCPUs that can be allocated to each OSE.
Additional core licenses can be assigned to a fully licensed server to increase the maximum number of VMs permitted to run SQL Server software. Each additional core license allows deployment of SQL Server software in one additional VM.
Maximum virtualization can be achieved via the SA Unlimited Virtualization benefit. Customers are permitted to run any number of instances of SQL Server 2019 Enterprise Edition software in an unlimited number of VMs on a server with all physical cores fully licensed with SQL Server Enterprise Edition and covered by Software Assurance.
For more information about SQLServer Per Core licensing model see the Microsoft SQL Server 2019 Licensing guide.
The Server + CAL licensing model is applicable to SQL Server Standard Edition only. In order to license SQL Server Standard Edition software under the Server + CAL licensing model customers need to purchase a server license for each operating system environment (physical server or VM) and a client access license (CAL) for each user (User CAL) and/or device (Device CAL) accessing SQL server or any of its components. A Device CAL is required for every device not operated by humans. For human operated devices, such as PCs, mobile phones, hand-held terminals, User CALs or a Device CALs can be used. A single CAL permits access to any number of licensed SQL servers.
SQL Server CALs are required for all users or devices that input data into, query, or view data from a SQL Server database either directly or indirectly (through a pooling device, an intermediary system or product, a web-based application, etc.). Such technique of aggregating or pooling connections to a SQL server is defined as “multiplexing”. Multiplexing does not reduce the number of CALs required. To learn more about multiplexing and its impact on SQL Server licensing see the Multiplexing - Client Access License (CAL) requirements brief.
In situations where users or devices can not be accurately counted the Per Core licensing model should be used.
For more information about SQLServer Server + CAL licensing model see the Microsoft SQL Server 2019 Licensing guide.
Containers and virtual machines are considered the same form the licensing perspective.
All rules and conditions applicable to VMs under the Per Core and Server + CAL
licensing models are also applicable to containers.
Any Operating System Environment (OSE) running any of the licensed SQL Server components must be fully licensed.The list of licensed components includes:
Management tools and other software identified as Additional Software in the Licensing Terms can be generally distributed and run on any number of devices for use with a licensed instance of SQL Server software.
There are two distinct mobility-related Software Assurance benefits - License Mobility Across Server Farms and License Mobility through Software Assurance. License Mobility benefits are available for all editions of SQL Server 2019 under the Per Core and Server+CAL licensing models.
With License Mobility Across Server Farms customers can reassign SQL Server licenses to different servers within a server farm as often as needed.
With License Mobility through Software Assurance customers can reassign licenses, once every 90 days, to servers in another server farm or to third party shared servers (non-private cloud). In the latter case additional rules and conditions apply. For more details see the License Mobility through Software Assurance Customer Program Guide.
For each SQL Server Core licence with active SA coverage customers can use one virtual core in a VM (OSE) deployed on the third party shared server infrastructure, subject to a minimum of 4 core licenses per VM.
For each SQL Server licence (Server + CAL licensing model) with active SA coverage, customers can deploy one VM (OSE) on the third party shared server infrastructure. In this scenario SQL CALs must have active SA coverage as well.
Without SA:
Note: In this context server farm means a single data center or two data centers each physically located either in time zones not more than four hours apart, or within the European Union (EU) and/or European Free Trade Association (EFTA). A data center can be moved from one Server Farm to another, but not on a short-term basis. A given data center may only be part of one server farm.
As per the SQL Server 2019 pricing page the approximate costs for different license types are as follows (US$):
The yearly Software Assurance cost can be estimated at 25% of the base license cost.