Examples: SQL Server Licensing
The following examples show how License Analytics enforces SQL Server licensing rules in common scenarios.
SQL Server Example 1A: Processor-licensed SQL Server, Continuous SA Coverage, Evaluated in 2017
- Scenario:
You acquired 4 processor licenses for SQL Server 2008 R2 Enterprise under an Enterprise Agreement with SA.
- What licensing rules apply?
In 2012, SQL Server licensing switched from processor to core licensing. Customers with SA who continued SA coverage were converted to core licensing at the first SA renewal (within three years) after April 1, 2012. This means that SQL Server 2008 R2 licensing is now core-based. If the core conversion factor is four core licenses per processor license, you now have the right to run SQL Server 2008 R2 Enterprise (or any earlier or later Enterprise edition version) on a 16-core machine.
SQL Server Example 1B: Processor-licensed SQL Server, No SA Coverage, Evaluated in 2017
- Scenario:
You acquired 4 processor licenses for SQL Server 2008 R2 Enterprise under a Select Agreement (no SA).
- What licensing rules apply?
The rules are the same as when the software was purchased. If running on a four-processor (physical) machine, you have the right to run as many guest VMs with SQL Server installed as desired, which are the original license rules. These rights apply to any earlier version of SQL Server Enterprise.
SQL Server Example 2A: Server+CAL-licensed SQL Server, Continuous SA Coverage, Evaluated in 2017
- Scenario:
You acquired one Server license (in a Server+CAL scheme) for SQL Server 2008 R2 Enterprise under an Enterprise Agreement (with SA). SA coverage has been continuous since the acquisition.
- What licensing rules apply?
The rules have changed, but in a different way. You still have the right to install and run SQL Server Enterprise (any version) using a Server+CAL distribution. The software is internally (technically) limited to execute on 20 cores. The big difference is in the virtualization rights. Rather than licensing unlimited VM guests running SQL Server Enterprise, the license terms now allow only four VM guests running SQL Server for every Server+CAL license assigned to the VM host.
SQL Server Example 2B: Server+CAL-licensed SQL Server, No SA Coverage, Evaluated in 2017
- Scenario:
You acquired one Server license (in a Server+CAL scheme) for SQL Server 2008 R2 Enterprise under a Select Agreement (no SA).
- What licensing rules apply?
The original license rules apply: You can run SQL Server 2008 R2 Enterprise on a single server with as many VM guests (running SQL Server) as desired. CALs for SQL Server 2008 R2 are required for access.
SQL Server Example 3: Core-licensed SQL Server, SA Coverage, Evaluated in 2017
- Scenario:
You acquired 32 core licenses for SQL Server 2012 Standard under a Select Agreement incorporating SA. SA coverage has been in force continuously since then. You installed SQL Server 2016 Standard.
- What licensing rules apply?
The license terms for SQL Server Standard are the same in 2016 as when the original software was purchased. You have the right to run any version of SQL Server Standard on a 32 core machine, or on two 16-core machines (based on minimum rules for cores per processor). SQL Server licenses are sold as a two-core package. In this case, you ordered 16 2-core licenses, which offers licenses for 32 cores. There are specific rules related to licensing or running in guest VMs (see Virtual Machines and License Analytics).
SQL Server Example 4: Lapsed SA Coverage
If you purchased products under an SA agreement that has since lapsed, the license rules in effect when the last SA renewal occurred are in force. This means that you can use any version of SQL Server released before SA coverage lapsed. The license rules are those in force as of the contract's last effective date. This means that License Analytics will compute time-limited upgrade requirements (example: from SQL Server 2008 R2). If entitlements for SQL Server 2012 are available, these entitlements are expressed in cores (the "preferred units" for SQL Server 2012).