Executive Summary

In today’s fast-paced and data-driven world, businesses rely heavily on robust database management systems, and
Microsoft SQL Server stands as a leading choice for many. However, the cost associated with SQL Server licensing often
presents a significant financial challenge for companies. This white paper delves into the complexities and substantial
expenses involved in SQL Server licensing, aiming to provide a comprehensive understanding and strategies for cost
rationalisation.
The primary factors contributing to the high cost of SQL Server licenses are twofold. First, the inherent cost of the license
itself is substantial. Microsoft's pricing model, which includes a variety of editions and licensing options, often leads to
confusion and can result in the selection of a more expensive licensing option than necessary. Second, and equally crucial,
is the issue of insufficiently planned installations within the IT environment. A lack of strategic planning often leads to
over-provisioning, where more licenses are purchased than are actually needed, or under-utilisation, where the full
potential of the purchased licenses is not realised.
To effectively tackle the challenges associated with SQL Server licensing costs, a comprehensive and diverse strategy is
essential. This white paper provides a detailed guide on various methods and practices designed to maximise the value of
SQL Server license investments. It addresses the intimidating nature of these costs, highlighting that with the appropriate
strategies and insights, businesses can achieve substantial cost reductions.

Objective and Target Audience

The primary goal of this document is to empower IT leaders with crucial and reliable knowledge and tools that enable
them to adeptly manoeuvre through the intricacies of SQL Server licensing.
This white paper does not attempt to replace the official Microsoft documentation but to add much needed context and
clarity derived from experience running successful SAM programs and Microsoft license audits. This white paper should be
useful for Software Asset Managers, Software Licensing Specialists, IT Procurement, IT Service Providers, IT Managers, IT
Consultants, Analysts and CIOs.

Problem Statement
The increasing complexity of SQL Server environments arises from a range of factors, including diverse and ever-evolving
licensing models, the intricacies of SQL Server's specific licensing requirements, rapidly changing technology trends, and
the varied needs of businesses and end-users. SQL Server is used by 27.5% of organisations worldwide and is also
supported on Linux. As it gains more popularity it becomes more integral to business operations across industries.
Understanding and effectively managing these licenses is crucial.

SQL Server licensing has undergone significant changes, adapting to the shifting paradigms in software deployment and
usage. With options ranging from core-based licensing to server/CAL (Client Access License) models, and the more recent
cloud-based and hybrid scenarios, organisations are often challenged to identify the most cost-effective and compliant
licensing strategy. Each model has its specific considerations, such as core counts, virtualisation, and user access levels,
which can dramatically affect both cost and compliance.

Microsoft's enterprise software, particularly SQL Server, has experienced a trend of consistent price increases over the
years. These increases reflect not only Microsoft's strategy in evolving its product line-up but also the broader dynamics in
the enterprise software market. The recent history of Microsoft SQL Server's pricing indicates a notable increase that took
effect from January 1, 2023. This increase was the first significant change in pricing since the release of SQL Server 2012.
Specifically, Microsoft implemented a 10% price increase for on-premises editions of SQL Server Enterprise, Standard, and
Web across all purchasing channels. This adjustment was communicated to customers in late October 2022 and marked a
substantial change in Microsoft's pricing strategy, reflecting the added value and features over the past decade.

The price rise applies to various licensing models and affects Azure SQL customers using SQL Server licensing offers, such
as software subscriptions or License and Software Assurance. However, the Azure SQL pay-as-you-go rate was not subject
to this increase, given its recent launch at a higher price point compared to other offerings. For existing Software
Assurance customers, the price increase will not take effect until their renewal.
This shift in pricing strategy underscores the continual evolution of Microsoft's enterprise software offerings, mirroring
the industry's move towards more advanced and feature-rich solutions. The increase reflects the significant enhancements
in SQL Server's capabilities, particularly in its 2022 version, which includes new features like fully managed disaster
recovery through Azure SQL Managed Instance and a new pay-as-you-go billing model enabled by Azure Arc.
For businesses and IT asset management professionals, this change emphasises the importance of staying informed about
licensing costs and models. It also highlights the need for strategic planning around software investments, especially for
organisations heavily reliant on Microsoft's ecosystem.
Understanding the different SQL Server feature sets against organisational needs requires in-depth knowledge and
strategic planning. The growing preference for cloud environments, including Azure SQL Database, introduces new
licensing considerations and potential benefits, but also adds layers of complexity in terms of license management and
cost optimisation.

Most common issues

Navigating the realm of SQL Server licensing is fraught with potential pitfalls. Even seasoned IT professionals and decision-
makers can stumble upon various licensing challenges, leading to compliance issues and financial repercussions. Below are
some of the most common SQL Server licensing issues, accompanied by examples for better understanding.

Issue Symptom

Deploying a different edition than what is covered by the license agreement

is common. A notable example is a business running SQL Server Enterprise
edition while only having a license for the Standard edition. This leads to
Edition Mismatch three options: buying new licenses, acquiring Step-up licenses, or reinstalling
to the licensed edition. Conversely, running a lower edition (like Standard)
when owning a higher one (like Enterprise) is permissible under edition
downgrade rights, but still may require adherence to specific conditions.

Using a different version than the licensed one poses a risk. A typical scenario
involves using a more recent version of SQL Server than the one licensed,
Version Mismatch without the necessary Software Assurance coverage. Additionally, CALs
(Client Access Licenses) must match or be higher than the server software
version they access, and overlooking this can lead to non-compliance.

Incorrect administration of licensing use rights, especially in virtualised

Misapplying Licensing Use environments, can be problematic. For instance, a company might reassign
Rights SQL Server Enterprise edition licenses more frequently than allowed,
violating the specific reassignment rules and resulting in non-compliance.

SQL Server under the core licensing metric does not require users benefiting
from SQL reporting to have CALs (Client Access Licenses), it is typical that
organisations would use core metrics when covering public facing or highly
accessible SQL as the Per Core model allows access for an unlimited number
of users or devices to connect from either inside or outside an organisation’s
firewall.
Core vs Server + CAL
metrics
When licensing under the Server + CAL model however it is important to
consider the CAL requirements based on the fact Multiplexing does not
reduce the number of Microsoft licenses required. Users are required to have
the appropriate licenses, regardless of their direct or indirect connection to
SQL Server. E.g. SQL Server is serving as a CRM database, those accessing the
CRM would require CALs.

Overlooking Fully The SQL Server product family contains a set of stand-alone services that
Licensable Components require a full SQL Server license:

→ Analysis Services;
→ Data Quality Services;
→ Integration Services;
→ Master Data Services;
→ Reporting Services;

This misconception can lead to unintentional non-compliance. For instance, a

company might deploy SQL Server Reporting Services for enhanced data
 reporting, unaware that this requires a separate license, thus inadvertently
breaching licensing terms.

With the increasing adoption of cloud and hybrid environments, licensing

becomes even more complex. For example, organisations using SQL Server in
Licensing in Hybrid and a hybrid setup (partly on-premises, partly in the cloud) must understand how
Cloud Environments their licenses apply in both contexts. The use of Azure Hybrid Benefit, for
instance, allows leveraging existing on-premises licenses for Azure SQL
databases, but requires careful management to ensure compliance.

Software Assurance provides a range of benefits, including new version

Non-compliance with rights and mobility rights, but also comes with specific terms that must be
Software Assurance (SA) adhered to. A common issue is failing to renew SA in time or
Requirements misunderstanding its benefits, leading to scenarios where an organisation
might use features or versions not covered under their current agreement.

License mobility is a key benefit under Software Assurance, allowing licenses

to be moved between servers within a server farm or to third-party hosting
organisations. However, not all SQL Server licenses are eligible for this, and
Overlooking License
failing to understand these nuances can lead to compliance issues. An
Mobility through SA
example could be a company attempting to transfer a non-eligible SQL Server
license to a new server in a different server farm, unknowing that this
violates the SA terms.

SQL Server Developer Edition is often used for development and testing.
However, a frequent mistake is using it in a production environment, which is
Improper Use of Developer not permitted under its licensing terms. For instance, a small company might
Editions mistakenly deploy the Developer Edition for its production database,
thinking it's a cost-effective solution, when in fact it violates the licensing
agreement.

When using Subscriber Access Licenses (SAL), it’s common to forget to report
all authorized users. Each user or device accessing the SQL Server must be
counted, and failing to do so can result in underreporting and compliance
Common Reporting
risks.
Mistakes in Service
Provider License
Reporting incorrect license types or editions is a prevalent issue. For
Agreement (SPLA)
example, a service provider might report a Standard edition license while
actually using an Enterprise edition. This misreporting can lead to compliance
issues and potential penalties.

A common mistake is neglecting the minimum requirement of four core

licenses per VM or per physical CPU. This rule ensures that even small
Core Minimums
deployments are adequately licensed, and failing to comply can lead to
licensing shortfalls.

Using SQL Server Enterprise with Software Assurance (SA) allows for
unlimited virtualization on a host, which can be more cost-effective for
Edition Optimization
environments with many virtual machines. This can optimize costs and
simplify license management.

Without Software Assurance, the rules for virtualization are different. You
must have at least as many core licenses as there are VMs if the number of
Different Rules Without VMs exceeds the number of cores on the host. This requires careful planning
Software Assurance to ensure compliance and cost efficiency.

Check the FAQ for a side-by-side comparison.

The ability to deploy backup instances of SQL Server software for temporary
use in a server dedicated to disaster recovery is a benefit of Software
Assurance. When considering licensing requirements and entitlement
Disaster Recovery Rights allocation it is important that these software assurance benefits are
considered, and that if software assurance is not present that the failover
devices (passive) have sufficient license coverage for the primary (or active)
device.
Compliance Risk
Microsoft SQL Server is a critical component in many IT environments, spanning traditional datacenters, public clouds,
containerized environments, and virtualized environments. Ensuring compliance with Microsoft SQL Server licensing terms
and conditions is essential for IT leaders to effectively manage their licensing requirements and avoid potential penalties.

Q: What is Microsoft license compliance verification (commonly known as “audit”)?

A: Microsoft license compliance verification (commonly known as “audit”) is a formal, mandatory

compliance review of a company's use of Microsoft products and services, and it is part of the
Microsoft license and contract compliance program. Microsoft conducts industry-standard compliance
reviews with its business customers through an independent auditor pursuant to the terms of their
agreement. This review is an effort to help customers achieve and maintain license compliance, and to
protect Microsoft intellectual property rights. Therefore, be assured that unless Microsoft invokes its
contractual right to verify compliance via a third-party accounting firm (as fully documented in your
Volume Licensing Agreement), you are not involved in a license compliance verification.

Read the full FAQ: Source

Overview of Licensing Terms and Conditions

Microsoft SQL Server licensing is intricate, involving various factors such as the type of deployment, the number of cores,
and the edition of SQL Server being used. IT leaders must be familiar with these terms to allocate licenses appropriately
across their IT environments. Understanding bundling and exclusion scenarios is also crucial to avoid over- or under-
licensing.

💡 The Product Terms document outlines how Microsoft products, including SQL Server, can be utilized. IT leaders
should review these terms before assigning subscriptions across their environments.

Audit and Compliance Clauses

Enterprise Agreement

Microsoft includes audit rights in their Enterprise Agreement, similar to those seen in other enterprise software
agreements. The audit clause is typically found in Section 10 of the Enterprise Agreement under “Compliance Verification.”
The clause generally includes the following provisions:

Microsoft Enterprise Agreement

e.g.

Compliance Verification: During the term of this agreement and for a period of one (1) year
thereafter, Microsoft may, at its expense, verify compliance with the terms of the agreement. This
verification may include an audit of your use of the software and access to associated records and
systems.

Universal License Terms

This clause indicates that Microsoft reserves the right to employ technical mechanisms to ensure that customers adhere to
the terms of their software licenses. These technical measures might include methods such as software activation,
validation processes, and the use of product keys. Additionally, Microsoft can verify whether customers are complying
with the licensing terms outlined in their volume license agreement. Essentially, this means Microsoft can audit the
customer’s use of its software to confirm that it aligns with the agreed-upon licensing terms.

Universal License Terms > For all Software

e.g.

“Microsoft may use technical measures to enforce terms that restrict Customer’s use of certain
versions of Product and may verify compliance with those terms as provided in Customer’s volume
license agreement.”

Audit Process
1. Notice: Microsoft will provide at least thirty (30) days prior written notice before conducting any audit.

2. Scope and Cooperation: You are required to provide reasonable access to facilities, systems, and records to verify
compliance. This includes making personnel available to facilitate the audit process.

3. Resolution of Non-Compliance: If an audit reveals any non-compliance, you must resolve the issue within thirty (30)
days from the date of notice. This may involve purchasing additional licenses to cover any under-licensed usage.

4. Costs: If the audit reveals an underpayment exceeding five percent (5%) of the total license fees payable, you must also
reimburse Microsoft for the cost of the audit.

Maintaining compliance with Microsoft SQL Server licensing terms is crucial to avoid penalties and legal action and to
ensure smooth operation of IT environments. Regularly reviewing and understanding the Product Terms and being
prepared for potential audits can help mitigate compliance risks.

Problem Solving Process

The problem solving process can be structured into four logical parts:

1. Entitlement and contract analysis where we clarify three key aspects: the number of licenses we are entitled to use, the
specific types of these licenses, and the terms and conditions governing their use.

2. Deployment analysis where we determine the actual number of licenses used based on what is installed and how the
different SQL Server instances are configured and setup in the IT environment.

3. Reconciliation where we uncover the gaps, surplus and other possible issues by reconciling the license entitlements
with the used software licenses.

4. Optimisation and remediation scenarios, where we identify potential cost saving opportunities as well as ways to fix
any compliance issues.

Entitlement and Contract Analysis

A proper entitlement and contract analysis start with a complete inventory of the relevant data needed for the analysis.

Data Collection
For a proper analysis these are the go to sources to collect:

Microsoft Licensing Statement (MLS) which is requested from your Licensing Service Provider (LSP). This is often the
most reliable record of your entitlements;

Check for owned entitlement data that may be missing from the MLS under the following volume licensing programs:

Cloud Solution Provider;

 Open Value;

Microsoft Products and Services Agreement;

Microsoft Customer Agreement;

Microsoft Volume Licensing Service Center (VLSC) export. It’s worth noting that VLSC is transitioning to the Microsoft
365 admin center. Users accessing functionality in VLSC will have permissions to see and manage that same
functionality in a new volume licensing blade in Microsoft 365 admin center.

Microsoft Contracts;

Any other transactional documents: purchasing documents, invoices, purchasing orders etc.

Once collected these entitlement documents need to be properly stored, referenced and analysed and the information
consolidated into one single source of truth with references to the raw data.

Microsoft Licensing Statement analysis

The MLS is an estimate of license entitlements by product and version based on the Volume License agreements and
purchase transactions under those agreements (as reported by resellers to Microsoft).
The MLS is a document organised into several tabs, each serving a specific purpose in helping organisations understand
and manage their Microsoft licenses.

Tab Name Description

This tab is for verifying the scope of the License Statement, including the type
Organisation
of statement, organisations included, agreement names found, and search
Summary
keywords used.

License Here, you can review the summary of effective quantities by product and
Summary version to understand what licenses your organisation is entitled to use.

Transaction This tab allows for a quick view and filter of detailed transaction data included
Summary in the License Statement.

License Use this tab to further verify the scope of the License Statement by reviewing
Agreements the detailed list of agreements included.

Transaction This tab is useful for additional analysis of all transactions under the
Data Tab agreements included in the License Statement.

FAQ and This tab provides answers to common questions and definitions of
Glossary terminology.

⚠️ Limitations

The MLS only includes information for Microsoft licenses acquired through Volume Licensing programs and does
not cover licenses acquired via retail and/or Original Equipment Manufacturer (OEM) as well as other
procurement contracts noted below.

Licenses acquired in the last 45 days might not be included due to reseller reporting time frames.

License transfers recorded in hardcopy, such as those from mergers/acquisitions, may not be reflected in this
statement.

Enterprise Agreements are calculated using standard assumptions, which may not apply to every situation, and
agreements with non-standard terms may require additional review by a Microsoft representative.

When analysing the MLS, the main challenge lies in reconciling the License Summary tab with the Transaction Data tab as
there are often inconsistencies in the reported quantities. We recommend doing the analysis starting at transaction level
in order to fully understand how the license entitlements changed over time.
Entitlements missing from the MLS
The Microsoft Licensing Statement (MLS) is comprehensive, but there are instances where it might not include all owned
entitlement data, especially under certain volume licensing programs. Here's more detail on each:

Program Details

The CSP program allows organisations to purchase Microsoft cloud

services through third-party providers. Licenses acquired through CSP
might not always be reflected in the MLS, as they are managed and
Cloud Solution Provider invoiced directly by the CSP partner rather than Microsoft.
(CSP)
Contact your CSP partner directly. They should be able to provide
detailed reports of all Microsoft cloud services purchased through their
program.

This program is designed for small to medium-sized organisations that

want a simple and flexible way to purchase Microsoft software licenses.
Open Value agreements might not be fully captured in the MLS,
particularly if they involve software assurance or spread payments.
Open Value

For Open Value licensing, reach out to your Microsoft representative or

LSP. They can provide detailed reports and confirm whether all relevant
data is included in your MLS.

MPSA is a transactional licensing agreement for commercial,

government, and academic organisations. MPSA consolidates Microsoft
cloud services, software, and Microsoft Software Assurance. Some details
Microsoft Products and of MPSA, especially recent transactions or specific service agreements,
Services Agreement (MPSA) may not be immediately updated in the MLS.

Access the MPSA Portal. You can view and manage your agreements,
download statements, and track purchases here.

This is a simplified purchase agreement that provides consistent

purchase terms for all customers. Since this agreement is relatively new
and streamlined, some of the finer details or specific entitlements might
Microsoft Customer not be fully integrated into the MLS data.
Agreement
Information can typically be obtained through the Azure Portal or by
contacting your Microsoft account manager. They can guide you in
accessing detailed reports related to this agreement.

The ESA is a licensing program that provides organizations with

subscription-based access to Microsoft software and services, allowing
Enterprise Subscription
for greater flexibility and scalability. It offers cost-effective solutions
Agreement (ESA)
through predictable payments and the ability to adjust license counts
based on changing business needs.

The SC is a licensing program designed for organizations that want to

standardize on Microsoft's server and cloud technologies, offering
Server and Cloud Enrollment benefits such as simplified license management, cost savings, and access
(SCE) to the latest innovations. SCE includes discounted pricing for committing
to Microsoft's core server and cloud products, along with enhanced
benefits for Software Assurance.

Microsoft VLSC export analysis

The Microsoft Volume Licensing Service Center (VLSC) is an online platform provided by Microsoft for managing volume
licensing agreements, downloading licensed software, and accessing volume license keys.
The VLSC export is typically organised into two tabs, each serving a specific purpose in helping organisations understand
and manage their Microsoft licenses.

Tab Name Description

 This tab is designed to give an overview of your organisation's entire volume
licensing agreement with Microsoft. It includes details like the agreement
number, end dates of the agreement, and the Program under which the
Relationship licenses were purchased.
Summary
It helps in tracking and managing the overall contractual relationship with
Microsoft. It's particularly useful for getting a quick snapshot of the licensing
agreement's status and understanding the scope of the licenses held.

This tab focuses on the specifics of the licenses themselves. It provides

detailed information about each license type your organisation has acquired,
including the quantity, product name, version, and active SA quantity.
License
Summary It is crucial for asset management, as it allows you to monitor the usage and
allocation of Microsoft licenses within your organisation. It's also helpful for
compliance purposes, ensuring that you are using the software within the
terms of the license agreement.

Microsoft Contracts
Microsoft license contract analysis is a crucial process for organisations to understand, manage, and optimise their use of
Microsoft software products.

Understanding Microsoft Volume Licensing Models

Program Details

For small to medium businesses; allows purchasing as needed over a two-year

Open License Program
agreement.

Open Value Offers the option of annual payments and includes Software Assurance.

For larger organisations that want to license software organisation-wide over

Enterprise Agreement (EA) a three-year period. Includes options for cloud services and software
assurance.

For government, academic, charitable, and corporate entities, allowing them

Select Plus
to purchase licenses at any time during the agreement term.

Components of a License Contract Analysis

Program Details

Reviewing the licenses owned, including their types, quantities, and the rights
License Entitlements
associated with them.

Understanding the specific conditions under which the software can be used,
Use Rights including installation, access, and deployment rights. This may vary based on
the type of license (e.g., OEM, Retail, Volume Licensing).

Identifying any specific limitations or conditions imposed by the license

Special Clauses and
agreement, such as geographical restrictions, audit clauses, downgrade rights,
Restrictions
or restrictions on the transfer of licenses.

Identifying areas for cost savings, such as unused licenses or opportunities to

switch to different licensing models, consolidate contract or change
Optimisation Opportunities purchasing channels for higher discounts. This also includes assessing needs
for upgrades or downgrades, and evaluating potential benefits from Software
Assurance or other maintenance programs.

Transactional Documents
Transactional documents like purchasing documents, invoices, and purchase orders are complementary to the rest of the
data and create a more reliable source of truth. Here's why:

Purchasing Documents: These documents provide proof of purchase and often detail the specific licenses and
quantities purchased. They are essential for verifying the accuracy of MLS data and can be used to identify any
 discrepancies.

Invoices: Invoices offer a financial record of the transactions, including the cost and the terms of purchase. They are
useful for budgeting and financial planning, as well as for compliance audits.

Purchase Orders: Purchase orders are official documents issued by a buyer committing to pay the seller for the sale of
specific products or services to be delivered in the future. They serve as a legal offer and can be used to track the
procurement of licenses and ensure they align with organisational needs and licensing agreements.

🔍 Finding your Purchasing Documents, Invoices, and Purchase Orders…

These are typically managed by your organisation's procurement or finance department.

Internal Records: Request copies of these documents from the department responsible for software
procurement.

Vendor Communication: If there are missing documents or further clarifications needed, contact the vendors
or resellers directly. They should be able to provide copies of past transactional documents.

Deployment Analysis
A proper entitlement and contract analysis start with a complete discovery and inventory of the devices in scope for the
analysis for the analysis.

Data Collection
Discovering and scanning all the devices in scope is not an easy task, especially in large environments. There’s a wide
variety of tools and data sources one could leverage to collect the necessary data for a complete technical analysis.
These are the most common data sources and tools that have worked great for us in the past based on our experience:

Source Data Type Description

A comprehensive IT management suite that allows for

detailed tracking and management of software and
hardware assets across a network. It is particularly
effective in environments heavily utilising Microsoft
products.

Microsoft System
Software Inventory SCCM has a Microsoft SQL database component which
Center Configuration
Hardware Inventory hosts all the data. This database can be queries to
Manager (SCCM)
extract the necessary information. Read more here.

⚠️ Warning: SCCM does not collect the SQL Server

edition. This has to be collected separately. Although a
popular tool, we don’t recommend SCCM as your main
data collection tool for SQL Server.

A directory service for Windows domain networks that

helps in managing and storing information about
Microsoft Active Software Inventory
network resources such as computers, users, and
Directory (AD) Hardware Inventory
services, and enforcing security policies for accessing
these resources.

The Microsoft Assessment and Planning Toolkit is a

discontinued agentless data collection and assessment
tool that collects a comprehensive inventory tool for
Software Inventory Windows.
MAP Toolkit Hardware Inventory
Virtualisation MAP provides a set of standard reports which can be
exported in Excel format. However, it also gives the
option to do a database dump (SQL Server Lite) which
can be imported and queried for additional information.

Lansweeper Software Inventory Lansweeper is an agent and agentless tool for collecting
Hardware Inventory all of the information required for a complete Microsoft
 Virtualisation analysis.

The data can be exported from the existing standard

reports or, it can be exported using a custom query
report.

Software Inventory Proactivanet is an agent based tool which can be a great

Proactivanet Hardware Inventory alternative to Lansweeper. It collects all of the
Virtualisation information required for a complete Microsoft analysis.

Snow is one of the most popular SAM tools out there,

and it’s great for collecting the relevant information for
a complete Microsoft analysis.
Software Inventory
Snow License
Manager
Hardware Inventory
Virtualisation
⚠️ Warning: Snow’s core analysis is known to be
problematic. Based on our experience so far, users
prefer to employ alternative methods for analysing the
data (e.g. manually or using a different tool).

ServiceNow SAM module also does a great job at

collecting all of the relevant information for a complete
Microsoft analysis.
Software Inventory
ServiceNow SAM Hardware Inventory ⚠️ Warning: ServiceNow’s analysis capabilities are
Virtualisation known to be limited. Based on our experience so far,
users prefer to employ alternative methods for
analysing the data (e.g. manually or using a different
tool).

RVTools is a popular and free VMware scanning and

monitoring tool developed by Rob T. and acquired by
Dell in 2023.

RVTools Virtualisation
The tools is still available for free, and it provides a
comprehensive report containing all of the relevant
information for creating a complete VMware
infrastructure topology.

Microsoft Hyper-V offers the possibility to export

Microsoft Hyper-V Virtualisation standard reports with the relevant virtualisation
information.

A proper entitlement and contract analysis start with a complete discovery and inventory of the devices in scope for the
analysis for the analysis.

Data Collection
Discovering and scanning all the devices in scope is not an easy task, especially in large environments. There’s a wide
variety of tools and data sources one could leverage to collect the necessary data for a complete technical analysis.
These are the most common data sources and tools that have worked great for us in the past based on our experience:

Source Data Type Description

Microsoft System Software Inventory A comprehensive IT management suite that allows for
Center Configuration Hardware Inventory detailed tracking and management of software and
Manager (SCCM) hardware assets across a network. It is particularly
effective in environments heavily utilising Microsoft
products.

SCCM has a Microsoft SQL database component which

hosts all the data. This database can be queries to
extract the necessary information. Read more here.

⚠️ Warning: SCCM does not collect the SQL Server

edition. This has to be collected separately. Although a
 popular tool, we don’t recommend SCCM as your main
data collection tool for SQL Server.

A directory service for Windows domain networks that

helps in managing and storing information about
Microsoft Active Software Inventory
network resources such as computers, users, and
Directory (AD) Hardware Inventory
services, and enforcing security policies for accessing
these resources.

The Microsoft Assessment and Planning Toolkit is a

discontinued agentless data collection and assessment
tool that collects a comprehensive inventory tool for
Software Inventory Windows.
MAP Toolkit Hardware Inventory
Virtualisation MAP provides a set of standard reports which can be
exported in Excel format. However, it also gives the
option to do a database dump (SQL Server Lite) which
can be imported and queried for additional information.

Lansweeper is an agent and agentless tool for collecting

all of the information required for a complete Microsoft
Software Inventory analysis.
Lansweeper Hardware Inventory
Virtualisation The data can be exported from the existing standard
reports or, it can be exported using a custom query
report.

Software Inventory Proactivanet is an agent based tool which can be a great

Proactivanet Hardware Inventory alternative to Lansweeper. It collects all of the
Virtualisation information required for a complete Microsoft analysis.

Snow is one of the most popular SAM tools out there,

and it’s great for collecting the relevant information for
a complete Microsoft analysis.
Software Inventory
Snow License
Manager
Hardware Inventory
Virtualisation
⚠️ Warning: Snow’s core analysis is known to be
problematic. Based on our experience so far, users
prefer to employ alternative methods for analysing the
data (e.g. manually or using a different tool).

ServiceNow SAM module also does a great job at

collecting all of the relevant information for a complete
Microsoft analysis.
Software Inventory
ServiceNow SAM Hardware Inventory ⚠️ Warning: ServiceNow’s analysis capabilities are
Virtualisation known to be limited. Based on our experience so far,
users prefer to employ alternative methods for
analysing the data (e.g. manually or using a different
tool).

RVTools is a popular and free VMware scanning and

monitoring tool developed by Rob T. and acquired by
Dell in 2023.

RVTools Virtualisation
The tools is still available for free, and it provides a
comprehensive report containing all of the relevant
information for creating a complete VMware
infrastructure topology.

Microsoft Hyper-V offers the possibility to export

Microsoft Hyper-V Virtualisation standard reports with the relevant virtualisation
information.

SQL Server Licensing Model 2008 - 2022

Microsoft SQL Server Version and Support Timeline

Please check Appendix A1. SQL Server Release and built numbers for more information.

Microsoft SQL Server 2022

Reference: Microsoft SQL Server 2022 Licensing Guide

💡 Main changes comparing to previous version:

Microsoft SQL Server is increasingly being deployed in virtualized environments, which enable running instances
of SQL Server concurrently in separate virtual OSEs (or virtual machines).

SQL Server 2022 commercial editions

Edition Server + CAL Per Core Requirements

Standard ✅* ✅ *SQL Server CALs

required

Enterprise 🚫 ✅ ㅤ

Key capacity limits across SQL Server 2022 editions

Max Max Max Max

Max DB Max
Edition compute memory compute memory
Size DB Size
capacity utilization capacity utilization

Developer OS max OS max OS max OS max OS max OS max

4 GB
Lesser of 1 Lesser of 1
(Advanced
Express socket or 4 1410 MB 10 GB socket or 4 N/A
Services
cores cores
Edition)

64 GB
Lesser of 4
Standard 24 core (MOLAP)
128 GB 524 PB sockets or 64 GB
(Server +CAL) limit 16 GB
24 cores
(Tabular)

Standard
(Per Core) Lesser of 4 128 GB 524 PB Lesser of 4 64 GB 64 GB
sockets or sockets or (MOLAP)
24 cores 24 cores 16 GB
 (Tabular)

Enterprise
OS max OS max 524 PB OS max OS max OS max
(Per Core)

SQL Server 2022 Software Assurance

Benefit Description

Azure Hybrid Benefit for SQL Server is an Azure-based benefit

that enables customers to use SQL Server licenses with Software
Assurance or subscription licenses to pay a reduced rate (“base
Azure Hybrid Benefit rate”) on Azure SQL Database vCore-based options such as
managed instance, vCore-based single database, and vCore-
based elastic pool; on SQL Server in Azure Virtual Machines
(including, but not limited to, Azure Dedicated Host); and on SQL
Server Integration Services.

Allows customers to install and run passive SQL Server instances

Fail-Over servers for disaster recovery in a separate OSE or server for disaster recovery in anticipation
of a failover event.

Allows customers to install and run passive SQL Server instances

Fail-Over servers for disaster recovery
in a separate OSE or server for disaster recovery in Azure in
in Azure
anticipation of a failover event.

Allows customers to install and run passive SQL Server instances

Fail-Over servers for high availability in a separate OSE or server for high availability in anticipation of
a failover event.

Allows customers to run any number of instances of SQL Server

Unlimited virtualization (VMs) Enterprise Edition software in an unlimited number of VMs.
Applicable under the core licensing model only.

Allows customers to run any number of containers in a virtual

Unlimited containers
OSE when licensing by virtual OSE (virtual core licensing).
Available for Standard or Enterprise licenses.

Allows assignment of subscription licenses or licenses with

Flexible Virtualization Benefit Software Assurance to Authorized Outsourcers’ servers (shared
or dedicated) under expanded Outsourcing Software
Management rights.

Power BI Report Server Allows SQL Server Enterprise Edition customers to run Power BI
Report Server.

With subscription licenses or licenses with Software Assurance,

Option to license by virtual machine SQL Server 202 may be licensed by virtual machine, and licenses
may move with the virtual machine at any time as needed to
another server in the same server farm.

Allow reassignment of SQL Server licenses within a server farm

License Mobility within a server farm
more than once every 90 days. Does not apply to SQL Server
PDW.

Allows license reassignment of SQL Server to Authorized License

License Mobility through SA
Mobility Partners’ shared servers. Does not apply to SQL Server
PDW.

In addition to the benefits noted above, Server Cloud Enrollment

Additional benefits for SCE customers
(SCE) customers may also qualify for premium benefits, including
Unlimited Problem Resolution Support.

SQL Server 2022 Licensing Model

A. SQL Server 2022 Per Core

When running SQL Server in a physical OSE, all physical cores on the server must be licensed. Software partitioning does
not reduce the number of core licenses required, except when licensing individual virtual machines (VMs). A minimum of
four core licenses is required for each physical processor on the server.

To determine and acquire the correct number of core licenses needed, customers must:

1. Count the total number of physical cores in the server.

2. Purchase the appropriate number of core licenses required for the server. Core licenses are sold in packs of two, so
customers must divide the number of licenses required by two to determine the actual number of line items (licensing
SKUs) to order.

A.1. Licensing SQL Server 2022 individual virtual machines

Similar to the Per Core licensing model in physical OSEs, all virtual cores (v-cores) supporting virtual OSEs that are running
instances of SQL Server software must be licensed accordingly. To license individual VMs using the Per Core model,
customers must purchase a core subscription license or license with Software Assurance for each v-core (or virtual
processor, virtual CPU, virtual thread) allocated to the VM, subject to a four-core license minimum per VM.

For licensing purposes, a v-core maps to a hardware thread.

1. License the virtual cores in each virtual machine

2. There is a minimum of four core subscription licenses or licenses with Software Assurance required for each virtual
machine

💡 Note
Licensing individual VMs is the only licensing option available for SQL Server Standard Edition customers who are
running the software in a virtualized environment under the Per Core model.

B. SQL Server 2022 Server + CAL

When licensing the SQL Server Standard Edition software under the Server+CAL model, customers purchase a server
license for each server, and a client access license (CAL) for each device (Device CAL) and/or user (User CAL) accessing SQL
Server or any of its components. A CAL is not software; it is a license granting users and devices access to the SQL Server
software.

Under the Server+CAL licensing model, each operating system environment (OSE) running SQL Server software or any of
its components must have a SQL Server server license assigned to the physical server hosting the OSE. Each server license
allows customers to run any number of SQL Server instances in a single OSE, either physical or virtual.

B.1. Licensing SQL Server 2022 individual virtual machines

To license individual VMs using the Server+CAL model, customers simply purchase one server license for each VM running
SQL Server software, regardless of the number of virtual processors allocated to the VM.

Each user or device accessing SQL Server software, regardless of a virtual or physical deployment, requires a SQL Server
CAL (for the same or a later version).

1. License each virtual machine with a server license;

2. License each user or device with a CAL (for the same or a later version);

C. Licensing SQL Server 2022 for maximum virtualisation

With SQL Server Enterprise Edition, customers who have licensed all physical cores on the server can run an unlimited
number of instances of the software in a number of OSEs/containers (physical and/or virtual) equal to the number of core
licenses assigned to the server. For example, a four-processor server with four cores per processor—fully licensed with 16
core licenses—can run SQL Server software in up to 16 VMs, regardless of the number of virtual cores allocated to each
VM.

Customers who have licensed all the physical cores on the server and want to run SQL Server software in more VMs
than are permitted, can assign additional core licenses to the licensed server.

Each additional core license allows deployment of SQL Server software in an additional VM, so in the previous example,
a customer who wants to run SQL Server Enterprise Edition in 18 VMs would simply acquire and assign 18 core licenses
to that server.

On servers fully licensed (i.e., based on physical cores) under SQL Server Enterprise subscription licenses or licenses with
Software Assurance (SA) , customers’ use rights allow any number of instances of the software to run in any number of
OSEs/containers (physical or virtual). This benefit enables customers to deploy an unlimited number of VMs to handle
dynamic workloads and fully utilize hardware computing capacity.

💡 Note: This benefit ends when the subscription licenses or SA coverage expire(s).

1. Fully license the physical server with SQL Server Enterprise Edition core subscription licenses or licenses with Software
Assurance;

2. Deploy an unlimited number of virtual machines;

D. Licensing SQL Server 2022 in containers

SQL Server can be deployed on Linux and Docker platforms. This allows customers to not only choose their platform, but
also to deploy SQL Server in containers using Docker container technology

Containers provide operating system level virtualization that allows multiple isolated applications to be run on a single
system.

For licensing, an operating system environment is defined as all or part of an operating system instance, or all or part of a
virtual operating system instance which enables separate machine identity. Containers and virtual machines are structured
differently, but they are considered the same from a licensing perspective.

SQL Server 2022 - Step-ups, Upgrades / Downgrades

When licensing SQL Server software, several deployment options are available to support a variety of customer upgrade
scenarios.

Benefit Description

Version upgrade rights are offered with subscription licenses and as a Software
Assurance (SA) benefit for qualified licenses and allow customers access to upgrade
Upgrade their deployments at no additional cost. Existing SQL Server subscription licenses or
licenses covered by SA are automatically upgraded to licenses for the latest version of
the corresponding SQL Server edition.

Cross edition rights are currently available for certain SQL Server products only and
allow customers to deploy an alternate (usually lower) edition in place of the currently
licensed edition. SQL Server cross edition rights can be combined with the version
Cross Edition downgrade rights (available for all products offered under a Volume Licensing
Agreement) that allow customers to deploy prior versions of the software in place of
the currently licensed version. In some cases, rights to deploy prior versions of product
editions other than the edition currently licensed may also be allowed.

Edition step-ups are offered as a Software Assurance (SA) benefit in certain Volume
Licensing programs only and allow customers to move from a lower product edition.
Step-up SQL Server Standard Edition Core licenses can step-up to SQL Server Enterprise Edition
Core licenses only. To be eligible to step-up to a higher edition, the lower edition license
must be covered by SA. Step-Ups between licensing models are not allowed.
 💡 Note: When using version downgrade or cross edition deployment rights, the product use rights for the originally
licensed version and edition still apply.

Product Deployment Rights

SQL Server SQL Server Standard Server 2022 or earlier

2022 Standard SQL Server Workgroup 2008 R2 or earlier
(Server + CAL) SQL Server for Small Business 2008 R2 or earlier

SQL Server SQL Server Standard Core 2022 or earlier

2022 Standard SQL Server Web (non-SPLA only) 2008 R2 or earlier
(Per Core) SQL Server Workgroup 2008 R2 or earlier

SQL Server Enterprise Core 2022 or earlier

SQL Server
SQL Server Business Intelligence 2014 or earlier
2022 Enterprise
SQL Server Standard Core 2022 or earlier
(Per Core)
SQL Server Datacenter 2008 R2 or earlier

ℹ️ Deployment options available to customers with SQL Server 2022 licenses. SQL Server 2022 product terms apply.

Microsoft SQL Server 2019

Reference: Microsoft SQL Server 2019 Licensing Guide

💡 Main changes comparing to previous version:

SQL Server 2019 comes with Apache Spark and Hadoop Distributed File System (HDFS) for intelligence over all
your data.

SQL Server 2019 commercial editions

Edition Server + CAL Per Core Requirements

Standard ✅* ✅ *SQL Server CALs

required

Enterprise 🚫 ✅ ㅤ

Key capacity limits across SQL Server 2019 editions

Max Max Max Max

Max DB Max
Edition compute memory compute memory
Size DB Size
capacity utilization capacity utilization

Developer OS max OS max OS max OS max OS max OS max

4 GB
Lesser of 1 Lesser of 1
(Advanced
Express socket or 4 1 GB 10 GB socket or 4 N/A
Services
cores cores
Edition)

64 GB
Lesser of 4
Standard 24 core (MOLAP)
128 GB 524 PB sockets or 64 GB
(Server +CAL) limit 16 GB
24 cores
(Tabular)
 64 GB
Lesser of 4 Lesser of 4
Standard (MOLAP)
sockets or 128 GB 524 PB sockets or 64 GB
(Per Core) 16 GB
24 cores 24 cores
(Tabular)

Enterprise
OS max 12 TB 524 PB OS max OS max OS max
(Per Core)

SQL Server 2019 Software Assurance

Benefit Description

Big Data Node core entitlement Provide customers a limited Big Data Node core entitlement for
SQL Server 2019 Big Data Cluster.

Allows customers to install and run passive SQL Server 2019

Fail-Over servers for disaster recovery instances in a separate OSE or server for disaster recovery in
anticipation of a failover event.

Allows customers to install and run passive SQL Server 2019

Fail-Over servers for disaster recovery
instances in a separate OSE or server for disaster recovery in
in Azure
Azure in anticipation of a failover event.

Allows customers to install and run passive SQL Server 2019

Fail-Over servers for high availability instances in a separate OSE or server for high availability in
anticipation of a failover event

Allows customers to run any number of instances of SQL Server

Unlimited virtualization 2019 Enterprise Edition software in an unlimited number of VMs.
Applicable under the core licensing model only.

Allows SQL Server Enterprise Edition customers to run Power BI

Power BI Report Server
Report Server.

Allows SQL Server Enterprise Edition customers to run Machine

Machine Learning Server for Hadoop
Learning Server for Hadoop.

Allows reassignment of SQL Server 2019 licenses within a server

License Mobility within a server farm farm more than once every 90 days. Does not apply to SQL
Server PDW.

Allows license reassignment of SQL Server 2019 to third party

License Mobility through SA
shared servers. Does not apply to SQL Server PDW.

Allows access to new product features and functionality

SQL Server appliance updates between major appliance software releases. Applies to SQL
Server PDW deployments only.

In addition to the benefits noted above, Server Cloud Enrollment

Additional benefits for SCE customers (SCE) customers may also qualify for premium benefits, including
Unlimited Problem Resolution Support.

SQL Server 2019 Licensing Model

A. SQL Server 2019 Per Core

Under the Per Core licensing model, each server running SQL Server 2019 software or any of its components (such as
Reporting Services or Integration Services) must be assigned an appropriate number of SQL Server 2019 core licenses. The
number of core licenses needed, depends on whether customers are licensing the physical server or individual virtual
operating system environments (OSEs).

When running SQL Server in a physical OSE, all physical cores on the server must be licensed. Software partitioning does
not reduce the number of core licenses required, except when licensing individual virtual machines (VMs). A minimum of
four core licenses is required for each physical processor on the server.

To determine and acquire the correct number of core licenses needed, customers must:

1. Count the total number of physical cores in the server.

2. Purchase the appropriate number of core licenses required for the server. Core licenses are sold in packs of two, so
customers must divide the number of licenses required by two to determine the actual number of line items (licensing
SKUs) to order.

A.1. Licensing individual SQL Server 2019 virtual machines

As customers consolidate existing workloads and refresh hardware, they may find that a SQL Server instance uses only a
fraction of available system computing power. When deploying databases in virtual environments that require just a
fraction of a physical server, savings can be achieved by licensing individual virtual machines (VMs).

Similar to the Per Core licensing model in physical OSEs, all virtual cores (v-cores) supporting virtual OSEs that are running
instances of SQL Server 2019 software must be licensed accordingly.

To license individual VMs using the Per Core model, customers must purchase a core license for each v-core (or virtual
processor, virtual CPU, virtual thread) allocated to the VM, subject to a four-core license minimum per VM. For licensing
purposes, a v-core maps to a hardware thread.

1. License the virtual cores in each virtual machine

2. There is a minimum of four core licenses required for each virtual machine

Additional licenses are required when:

A single hardware thread is supporting multiple virtual cores. (A core license is required for each v-core.)

Multiple hardware threads are supporting a single virtual core simultaneously. (A core license allows a single v-core to
be supported by a single hardware thread.)

B. SQL Server 2019 Server + CAL

Under the Server+CAL licensing model, each operating system environment (OSE) running SQL Server 2019 software or
any of its components must have a SQL Server 2019 server license assigned to the physical server hosting the OSE. Each
server license allows customers to run any number of SQL Server instances in a single OSE, either physical or virtual.

Running SQL Server software on different hardware partitions or blades requires separate software licenses. Hardware
partitions and blades are considered to be separate servers for licensing purposes and SQL Server software licenses
cannot be assigned to more than one server at any time.

Devices not operated by humans require device CALs, even when connecting to SQL Server indirectly. For human operated
devices such as PCs or hand-held terminals, a user CAL or device CAL can be used.

💡 Note: The use of hardware or software that reduces the number of devices or users that directly access or use
the software (multiplexing/pooling) does not reduce the number of CALs required

B.1. Licensing SQL Server 2019 individual virtual machines

To license individual VMs using the Server+CAL model, customers simply purchase one server license for each VM running
SQL Server software, regardless of the number of virtual processors allocated to the VM.

1. License each virtual machine with a server license

2. License each user or device with a CAL

 💡 Note: Each user or device accessing SQL Server 2019 software, regardless of a virtual or physical deployment,
requires a SQL Server 2019 CAL.

C. Licensing SQL Server 2019 for maximum virtualisation

With SQL Server 2019 Enterprise Edition, customers who have licensed all physical cores on the server can run an unlimited
number of instances of the software in a number of OSEs (physical and/or virtual) equal to the number of core licenses
assigned to the server. For example, a four-processor server with four cores per processor—fully licensed with 16 core
licenses—can run SQL Server software in up to 16 VMs, regardless of the number of virtual cores allocated to each VM.

Customers who have licensed all the physical cores on the server and want to run SQL Server 2019 software in more
VMs than are permitted, can assign additional core licenses to the licensed server.

Each additional core license allows deployment of SQL Server software in an additional VM, so in the previous example,
a customer who wants to run SQL Server Enterprise Edition in 18 VMs would simply acquire and assign 18 core licenses
to that server.

With the addition of Software Assurance (SA) coverage on all Enterprise Edition core licenses (for a fully licensed server),
customers’ use rights are expanded to allow any number of instances of the software to run in any number of OSEs
(physical or virtual). This valuable SA benefit enables customers to deploy an unlimited number of VMs to handle dynamic
workloads and fully utilize hardware computing capacity.

1. Fully license the server with SQL Server 2019 Enterprise Edition core licenses and Software Assurance

2. Deploy an unlimited number of virtual machines

💡 Note: This benefit ends when SA coverage expires.

D. Licensing SQL Server 2019 in containers

Similar to the Per Core licensing model in physical OSEs, all virtual cores (v-cores) supporting containers running instances
of SQL Server 2019 software, must be licensed accordingly.

To license individual containers using the Per Core model, customers must purchase a core license for each v-core (or
virtual processor, virtual CPU, virtual thread) allocated to the container, subject to a four-core license minimum per
container. For licensing purposes, a v-core maps to a hardware thread.

💡 Note: Licensing individual containers is the only licensing option available for SQL Server 2019 Standard Edition
customers who are running the software in containers under the Per Core model.

For customers with high density container environments who want to move containers dynamically across servers to
reallocate resources as needed, Microsoft permits License Mobility as an exclusive SA benefit available for all SQL Server
editions. For more information on licensing for application mobility, refer to the Advanced licensing scenarios section of
this guide.

1. License the virtual cores in each container

2. There is a minimum of four core licenses required for each container

To license individual containers deployed using nested virtualization i.e. within a VM, customers must purchase a core
license for each v-core (or virtual processor, virtual CPU, virtual thread) allocated to the container, subject to a four-core
license minimum per container.
To license individual containers using the Server+CAL model customers simply purchase one server license for each
container running SQL Server software, regardless of the number of virtual processors allocated to the container.

1. License each container with a server license

2. License each user or device with a CAL

Licensing containers for maximum density

With SQL Server 2019 Enterprise Edition, customers who have licensed all physical cores on the server can run a number of
containers equal to the number of core licenses assigned to the server. For example, a four-processor server with four
cores per processor—fully licensed with 16 core licenses—can run SQL Server software in up to 16 containers, regardless
of the number of virtual cores allocated to each container.

Customers who have licensed all the physical cores on the server and want to run SQL Server 2019 software in more
containers than are permitted, can assign additional core licenses to the licensed server.

Each additional core license allows deployment of SQL Server software in an additional container, so in the previous
example, a customer who wants to run SQL Server Enterprise Edition in 18 containers would simply acquire and assign
18 core licenses to that server.

With the addition of Software Assurance (SA) coverage on all Enterprise Edition core licenses (for a fully licensed server),
customers’ use rights are expanded to allow any number of containers to run on the licensed server. This valuable SA
benefit enables customers to deploy an unlimited number of containers to handle dynamic workloads and fully utilize
hardware computing capacity.

1. Fully license the server with SQL Server 2019 Enterprise Edition core licenses and Software Assurance;

2. Deploy an unlimited number of containers;

💡 Note: This benefit ends when SA coverage expires.

Microsoft SQL Server 2017

Reference: Microsoft SQL Server 2017 Licensing Guide

💡 Main changes comparing to previous version:

Deployment on Linux and Docker platform introduced.

SQL Server 2017 commercial editions

Edition Server + CAL Per Core Requirements

Standard ✅* ✅ *SQL Server CALs

required

Enterprise 🚫 ✅ ㅤ

Key capacity limits across SQL Server 2017 editions

Max Max Max Max

Max DB Max
Edition compute memory compute memory
Size DB Size
capacity utilization capacity utilization

Developer OS max OS max OS max OS max OS max OS max

Express
Lesser of 1 1 GB 10 GB Lesser of 1 N/A 4 GB
 socket or 4 socket or 4 (Advanced
cores cores Services
Edition)

Lesser of 1 Lesser of 4
Web socket or 4 64 GB 524 PB sockets or N/A 64 GB
cores 16 cores

64 GB
Lesser of 4 Lesser of 4
Standard (MOLAP)
socket or 24 128 GB 524 PB sockets or 64 GB
(Core) 16 GB
cores 24 cores
(Tabular)

Enterprise
OS max 12 TB 524 PB OS max OS max OS max
(Per Core)

Enterprise
OS max 12 TB 524 PB 20 core limit OS max OS max
(Server + CAL)

SQL Server 2017 Software Assurance

Benefit Description

Allows customers to run any number of instances of SQL Server

Unlimited virtualization 2017 Enterprise Edition software in an unlimited number of VMs.
Applicable under the core licensing model only.

Allows customers to install and run passive SQL Server 2017

Failover Servers instances in a separate OSE or server for high availability in
anticipation of a failover event.

Allows SQL Server Enterprise Edition customers to run Power BI

Power BI Report Server
Report Server.

Allows SQL Server Enterprise Edition customers to run Machine

Machine Learning Server for Hadoop
Learning Server for Hadoop.

Allows reassignment of SQL Server 2017 licenses within a server

License Mobility within a server farm farm more than once every 90 days. Does not apply to SQL
Server PDW.

Allows license reassignment of SQL Server 2017 to third party

License Mobility through SA
shared servers. Does not apply to SQL Server PDW.

Allows backup instances of SQL Server 2017 software for

Disaster Recovery Rights
temporary use in a server dedicated to disaster recovery.

Allows access to new product features and functionality

SQL Server appliance updates between major appliance software releases. Applies to SQL
Server PDW deployments only.

In addition to the benefits noted above, Server Cloud Enrollment

Additional benefits for SCE customers (SCE) customers may also qualify for premium
benefits, including Unlimited Problem Resolution Support.

SQL Server 2017 Licensing Model

A. SQL Server 2017 Per Core

Under the Per Core licensing model, each server running SQL Server 2017 software or any of its components (such as
Reporting Services or Integration Services) must be assigned an appropriate number of SQL Server 2017 core licenses. The
number of core licenses needed, depends on whether customers are licensing the physical server or individual virtual
operating system environments (OSEs).

Unlike the Server+CAL licensing model, the Per Core model allows access for an unlimited number of users or devices to
connect from either inside or outside an organization’s firewall. With the Per Core model, customers do not need to
purchase additional client access licenses (CALs) to access the SQL Server software.

When running SQL Server in a physical OSE, all physical cores on the server must be licensed. Software partitioning does
not reduce the number of core licenses required, except when licensing individual virtual machines (VMs). A minimum of
four core licenses is required for each physical processor on the server.

To determine and acquire the correct number of core licenses needed, customers must:

1. Count the total number of physical cores in the server.

2. Purchase the appropriate number of core licenses required for the server. Core licenses are sold in packs of two, so
customers must divide the number of licenses required by two to determine the actual number of line items (licensing
SKUs) to order.

A.1. Licensing individual SQL Server 2017 virtual machines

Similar to the Per Core licensing model in physical OSEs, all virtual cores (v-cores) supporting virtual OSEs that are running
instances of SQL Server 2017 software must be licensed accordingly.

To license individual VMs using the Per Core model, customers must purchase a core license for each v-core (or virtual
processor, virtual CPU, virtual thread) allocated to the VM, subject to a four-core license minimum per VM. For licensing
purposes, a v-core maps to a hardware thread.

1. License the virtual cores in each virtual machine;

2. There is a minimum of four core licenses required for each virtual machine;

💡 Note: Licensing individual VMs is the only licensing option available for SQL Server 2017 Standard Edition
customers who are running the software in a virtualized environment under the Per Core model.

Additional licenses are required when:

A single hardware thread is supporting multiple virtual cores. (A core license is required for each v-core.)

Multiple hardware threads are supporting a single virtual core simultaneously. (A core license allows a single v-core to
be supported by a single hardware thread.)

B. SQL Server 2017 Server + CAL

Under the Server+CAL licensing model, each operating system environment (OSE) running SQL Server 2017 software or
any of its components must have a SQL Server 2017 server license assigned to the physical server Microsoft SQL Server
2017 Licensing guide 14 hosting the OSE. Each server license allows customers to run any number of SQL Server instances
in a single OSE, either physical or virtual.

Running SQL Server software on different hardware partitions or blades requires separate software licenses.
Hardware partitions and blades are considered to be separate servers for licensing purposes and SQL Server software
licenses cannot be assigned to more than one server at any time.

To access a licensed SQL Server, each user or device must have a SQL Server CAL that is the same version or newer than
the SQL Server software version being accessed.

Devices not operated by humans require device CALs, even when connecting to SQL Server indirectly. For human
operated devices such as PCs or hand-held terminals, a user CAL or device CAL can be used.
While being version-specific, each SQL Server 2017 CAL provides access to 1) any number of current and/or prior version
licensed SQL Server instances in a customer’s organization, and 2) current or previous product editions, including legacy
SQL Business Intelligence, SQL Server Enterprise, SQL Server Workgroup and SQL Server for Small Business edition
servers.

The use of hardware or software that reduces the number of devices or users that directly access or use the software,
multiplexing/pooling, does not reduce the number of CALs required.

B.1. Licensing SQL Server 2017 individual virtual machines

To license individual VMs using the Server+CAL model, customers simply purchase one server license for each VM running
SQL Server software, regardless of the number of virtual processors allocated to the VM.
For example, a customer who wants to deploy Standard Edition running in six VMs, each allocated with four v-cores, would
need to assign six SQL Server 2017 Standard server licenses to that server.

1. License each virtual machine with a server license;

2. License each user or device with a CAL

💡 Note: Each user or device accessing SQL Server 2017 software, regardless of a virtual or physical deployment,
requires a SQL Server 2017 CAL

C. Licensing SQL Server 2017 for maximum virtualisation

With SQL Server 2017 Enterprise Edition, customers who have licensed all physical cores on the server can run an
unlimited number of instances of the software in a number of OSEs (physical and/or virtual) equal to the number of core
licenses assigned to the server. For example, a four-processor server with four cores per processor—fully licensed with
sixteen core licenses—can run SQL Server software in up to sixteen VMs, regardless of the number of virtual cores
allocated to each VM.

Customers who have licensed all the physical cores on the server and want to run SQL Server 2017 software in more
VMs than are permitted, can assign additional core licenses to the licensed server.

Each additional core license allows deployment of SQL Server software in an additional VM, so in the previous example,
a customer who wants to run SQL Server Enterprise Edition in eighteen VMs would simply acquire and assign eighteen
core licenses to that server.

With the addition of Software Assurance (SA) coverage on all Enterprise Edition core licenses (for a fully licensed server),
customers’ use rights are expanded to allow any number of instances of the software to run in any number of OSEs
(physical or virtual). This valuable SA benefit enables customers to deploy an unlimited number of VMs to handle dynamic
workloads and fully utilize hardware computing capacity. This benefit ends when SA coverage expires.

1. Fully license the server with SQL Server 2017 Enterprise Edition core licenses and Software Assurance;

2. Deploy an unlimited number of virtual machines;

Microsoft SQL Server 2016

Reference: Microsoft SQL Server 2016 Licensing Guide

💡 Main changes comparing to previous version:

BI edition discontinued;

SQL Server 2016 commercial editions

Edition Server + CAL Per Core Requirements
Standard ✅* ✅ *SQL Server CALs
required

Enterprise 🚫 ✅ ㅤ

Key capacity limits across SQL Server 2016 editions

Max Max Max Max

Max DB Max
Edition compute memory compute memory
Size DB Size
capacity utilization capacity utilization

Developer OS max OS max OS max OS max OS max OS max

4 GB
Lesser of 1 Lesser of 1
(Advanced
Express socket or 4 1 GB 10 GB socket or 4 N/A
Services
cores cores
Edition)

Lesser of 1 Lesser of 4
Web socket or 4 64 GB 524 PB sockets or N/A 64 GB
cores 16 cores

64 GB
Lesser of 4 Lesser of 4
Standard (MOLAP)
socket or 24 128 GB 524 PB sockets or 64 GB
(Core) 16 GB
cores 24 cores
(Tabular)

Enterprise
OS max 12 TB 524 PB OS max OS max OS max
(Per Core)

Enterprise
20 core limit 12 TB 524 PB 20 core limit OS max OS max
(Server + CAL)

SQL Server 2016 Software Assurance

Benefit Description

Allows customers to run any number of instances of SQL Server

Unlimited Virtualization 2016 Enterprise Edition software in an
unlimited number of VMs. Applicable under the core licensing
model only.

Allows customers to install and run passive SQL Server 2016

Failover Servers instances in a separate OSE or server for high availability in
anticipation of a failover event.

Allows reassignment of SQL Server 2016 licenses within a server

License Mobility within a
farm more than once every 90 days. Does not apply to SQL
Server Farm
Server PDW.

License Mobility through Software Allows license reassignment of SQL Server 2016 to third party
Assurance shared servers. Does not apply to SQL Server PDW.

Allows backup instances of SQL Server 2016 software for

Disaster Recovery Rights
temporary use in a server dedicated to disaster recovery.

Special Migration Offers Provides license grants and additional use terms for legacy SQL
Server 2008 R2 customers who are still migrating to current SQL
 Server 2016 product editions and license models.

Allows access to new product features and functionality

SQL Server Appliance Updates between major appliance software releases. Applies to SQL
Server PDW deployments only.

In addition to the benefits noted above, Server Cloud Enrollment

Additional Benefits for SCE Customers (SCE) customers may also qualify for premium benefits, including
Unlimited Problem Resolution Support.

SQL Server 2016 Licensing Model

A. SQL Server 2016 Per Core

Under the Per Core licensing model, each server running SQL Server 2016 software or any of its components (such as
Reporting Services or Integration Services) must be assigned an appropriate number of SQL Server 2016 core licenses. The
number of core licenses needed depends on whether customers are licensing the physical server or individual virtual
operating system environments (OSEs).

Unlike the Server+CAL licensing model, the Per Core model allows access for an unlimited number of users or devices to
connect from either inside or outside an organization’s firewall. With the Per Core model, customers do not need to
purchase additional client access licenses (CALs) to access the SQL Server software.

When running SQL Server in a physical OSE, all physical cores on the server must be licensed. Software partitioning does
not reduce the number of core licenses required, except when licensing individual virtual machines (VMs).

A minimum of four core licenses are required for each physical processor on the server.

To determine and acquire the correct number of core licenses needed, customers must:

1. Count the total number of physical cores in the server.

2. Purchase the appropriate number of core licenses required for the server. Core licenses are sold in packs of two, so
customers must divide the number of licenses required by two to determine the actual number of line items (licensing
SKUs) to order.

💡 Note: The use of hyper-threading technology does not affect the number of core licenses required when running
SQL Server software in a physical OSE.

A.1. Licensing individual SQL Server 2016 virtual machines

Similar to the Per Core licensing model in physical OSEs, all virtual cores (v-cores) supporting virtual OSEs that are running
instances of SQL Server 2016 software must be licensed accordingly.

To license individual VMs using the Per Core model, customers must purchase a core license for each v-core (or virtual
processor, virtual CPU, virtual thread) allocated to the VM, subject to a four core license minimum per VM. For licensing
purposes, a v-core maps to a hardware thread.

1. License the virtual cores in each virtual machine

2. A minimum of four core licenses is required for each virtual machine

💡 Note: For customers with highly virtualized environments who want to move VMs dynamically across servers to
reallocate resources as needed, Microsoft permits License Mobility as an exclusive Software Assurance benefit
available for all SQL Server editions.

Additional licenses are required when:

 A single hardware thread is supporting multiple virtual cores. (A core license is required for each v-core.)

Multiple hardware threads are supporting a single virtual core simultaneously. (A core license allows a single v-core to
be supported by a single hardware thread.)

B. SQL Server 2016 Server + CAL

When licensing the SQL Server 2016 Standard Edition software under the Server+CAL model, customers purchase a server
license for each server and a client access license (CAL) for each device (Device CAL) and/or user (User CAL) accessing SQL
Server or any of its components. A CAL is not software; it is a license granting users and devices access to the SQL Server
software.

Under the Server+CAL licensing model, each operating system environment (OSE) running SQL Server 2016 software or
any of its components must have a SQL Server 2016 server license assigned to the physical server hosting the OSE. Each
server license allows customers to run any number of SQL Server instances in a single OSE, either physical or virtual.

To access a licensed SQL Server, each user or device must have a SQL Server CAL that is the same version or newer than
the SQL Server software version being accessed. For example, to access a server running SQL Server 2016 software, a user
needs a SQL Server 2016 CAL.

While being version-specific, each SQL Server 2016 CAL provides access to any number of current and/or prior version
licensed SQL Server instances in a customer’s organization, current or previous product edition, including legacy SQL
Business Intelligence, SQL Server Enterprise, SQL Server Workgroup, and SQL Server for Small Business edition servers.

💡 Notes

1. Running SQL Server software on different hardware partitions or blades requires separate software licenses.
Hardware partitions and blades are considered to be separate servers for licensing purposes and SQL Server
software licenses cannot be assigned to more than one server at any time.

2. Devices not operated by humans require device CALs, even when connecting to SQL Server indirectly. For
human-operated devices such as PCs or hand-held terminals, a user CAL or device CAL can be used.

3. The use of hardware or software that reduces the number of devices or users that directly access or use the
software (multiplexing/pooling) does not reduce the number of CALs required. This multiplexing scenario.

B.1. Licensing SQL Server 2016 individual virtual machines

To license individual VMs using the Server+CAL model, customers simply purchase one server license for each VM running
SQL Server software, regardless of the number of virtual processors allocated to the VM.

1. License each virtual machine with a server license

2. License each user or device with a CAL

For example, a customer who wants to deploy Standard Edition running in six VMs, each allocated with four v-cores, would
need to assign six SQL Server 2016 Standard server licenses to that server.

💡 Note: Each user or device accessing SQL Server 2016 software, regardless of a virtual or physical deployment,
requires a SQL Server 2016 CAL.

C. Licensing SQL Server 2016 for maximum virtualisation

With SQL Server 2016 Enterprise Edition, customers who have licensed all physical cores on the server can run an unlimited
number of instances of the software in a number of OSEs (physical and/or virtual) equal to the number of core licenses
assigned to the server. For example, a four-processor server with four cores per processor—fully licensed with 16 core
licenses—can run SQL Server software in up to 16 VMs, regardless of the number of virtual cores allocated to each VM.

Customers who have licensed all the physical cores on the server and want to run SQL Server 2016 software in more
VMs than are permitted can assign additional core licenses to the licensed server.

Each additional core license allows deployment of SQL Server software in an additional VM, so in the previous example,
a customer who wants to run SQL Server Enterprise Edition in 18 VMs would simply acquire and assign 18 core licenses
to that server.

With the addition of Software Assurance coverage on all Enterprise Edition core licenses (for a fully licensed server),
customers’ use rights are expanded to allow any number of instances of the software to run in any number of OSEs
(physical or virtual). This valuable Software Assurance benefit enables customers to deploy an unlimited number of VMs to
handle dynamic workloads and fully utilize hardware computing capacity. This benefit ends when Software Assurance
coverage expires.

Microsoft SQL Server 2014

Reference: Microsoft SQL Server 2014 Licensing Guide

SQL Server 2014 commercial editions

Edition Server + CAL Per Core Requirements

Standard ✅* ✅ *SQL Server CALs

required

Business Intelligence ✅ 🚫 ㅤ

Enterprise 🚫 ✅ ㅤ

Parallel Data
Warehouse
🚫 ✅ ㅤ

Key capacity limits across SQL Server 2014 editions

Max Max Max Max

Max DB Max
Edition compute memory compute memory
Size DB Size
capacity utilization capacity utilization

Developer OS max OS max OS max OS max OS max OS max

4 GB
Lesser of 1 Lesser of 1
(Advanced
Express socket or 4 1 GB 10 GB socket or 4 N/A
Services
cores cores
Edition)

Lesser of 1 Lesser of 4
Web socket or 4 64 GB 524 PB sockets or N/A 64 GB
cores 16 cores

Lesser of 4 Lesser of 4
Standard
socket or 16 128 GB 524 PB sockets or 64 GB 64 GB
(Core)
cores 16 cores

Business
Intelligence Lesser of 4 128 GB 524 PB OS max OS max OS max
(Server + CAL) socket or 16
 cores

Enterprise
OS max 12 TB 524 PB OS max OS max OS max
(Per Core)

Enterprise
20 core limit 12 TB 524 PB 20 core limit OS max OS max
(Server + CAL)

SQL Server 2014 Software Assurance

Benefit Description

Allows customers to run any number of instances of SQL Server

Unlimited Virtualization 2014 Enterprise Edition software in an
unlimited number of VMs. Applicable under the core licensing
model only.

Allows customers to install and run passive SQL Server 2016

Failover Servers instances in a separate OSE or server for high availability in
anticipation of a failover event.

Allows reassignment of SQL Server 2014 licenses within a server

License Mobility within a
farm more than once every 90 days. Does not apply to SQL
Server Farm
Server PDW.

License Mobility through Software Allows license reassignment of SQL Server 2014 to third party
Assurance shared servers. Does not apply to SQL Server PDW.

Allows backup instances of SQL Server 2014 software for

Disaster Recovery Rights
temporary use in a server dedicated to disaster recovery.

Provides license grants and additional use terms for legacy SQL
Special Migration Offers Server 2008 R2 customers who are still migrating to current SQL
Server 2014 product editions and license models.

Allows access to new product features and functionality

SQL Server Appliance Updates between major appliance software releases. Applies to SQL
Server PDW deployments only.

In addition to the benefits noted above, Server Cloud Enrollment

Additional Benefits for SCE Customers (SCE) customers may also qualify for premium benefits, including
Unlimited Problem Resolution Support.

SQL Server 2014 Licensing Model

A. SQL Server 2014 Per Core

To determine and acquire the correct number of core licenses needed, customers must:

1. Count the total number of physical cores in the server.

2. Minimum of four core licenses is required for each physical processor on a physical server.

3. To determine the total number of licenses required for the server.

Multiply the number of cores by the appropriate core factor

Processor Type Core Factor

All processors not mentioned below 1

AMD Processors 31XX, 32XX, 33XX, 41XX, 42XX, 43XX, 61XX, 62XX, 63XX Series
Processors with 6 or more cores 0.75
 Single-Core Processors 4

Dual-Core Processors 2

4. Core licenses are sold in packs of two, so customers must divide the number of licenses required by two to determine
the actual number of line items (licensing SKUs) to order.

When running SQL Server in a physical OSE, all physical cores on the server must be licensed. Software partitioning does
not reduce the number of core licenses required, except when licensing individual virtual machines (VMs). The minimum
number of licenses required for each processor on the server still applies.

A.1. Licensing individual SQL Server 2014 virtual machines

To license individual VMs using the Per Core model, customers must purchase a core license for each v-core (or virtual
processor, virtual CPU, virtual thread) allocated to the VM, subject to a four core license minimum per VM. For licensing
purposes, a v-core maps to a hardware thread. When licensing individual VMs, core factors do not apply.

1. License the virtual core in each virtual machine

2. There is a minimum of four core licenses required for each virtual machine

💡 Note: Licensing individual VMs is the only licensing option available for SQL Server 2014 Standard Edition
customers who are running the software in a virtualized environment under the Per Core model.

B. SQL Server 2014 Server + CAL

Under the Server+CAL licensing model, each operating system environment (OSE) running SQL Server 2014 software or
any of its components must have a SQL Server 2014 server license assigned to the physical server hosting the OSE. Each
server license allows customers to run any number of SQL Server instances in a single OSE, either physical or virtual.

💡 Notes

1. Running SQL Server software on different hardware partitions or blades requires separate software licenses.
Hardware partitions and blades are considered to be separate servers for licensing purposes and SQL Server
software licenses cannot be assigned to more than one server at any time.

2. To access a licensed SQL Server, each user or device must have a SQL Server CAL that is the same version or
newer than the SQL Server software version being accessed.

3. Devices not operated by humans require device CALs, even when connecting to SQL Server indirectly. For
human operated devices such as PCs or hand-held terminals, a user CAL or device CAL can be used.

4. While being version-specific, each SQL Server 2014 CAL provides access to any number of current and/or prior
version licensed SQL Server instances in a customer’s organization, regardless of the platform (32-bit, 64-bit or
IA64) or product edition, including legacy SQL Server Workgroup and SQL Server for Small Business edition
servers.

B.1. Licensing SQL Server 2014 individual virtual machines

To license individual VMs using the Server+CAL model (available for SQL Server 2014 Standard and Business Intelligence
editions only) customers simply purchase one server license for each VM running SQL Server software, regardless of the
number of virtual processors allocated to the VM.

💡 Note: Each user or device accessing SQL Server 2014 software, regardless of a virtual or physical deployment,
requires a SQL Server 2014 CAL.
C. Licensing SQL Server 2014 for maximum virtualisation

With SQL Server 2014 Enterprise Edition, customers who have licensed all physical cores on the server can run an unlimited
number of instances of the software in a number of OSEs (physical and/or virtual) equal to the number of core licenses
assigned to the server. For example, a four processor server with four cores per processor—fully licensed with sixteen core
licenses—can run SQL Server software in up to sixteen VMs, regardless of the number of virtual cores allocated to each
VM.

1. Fully license the server SQL Server 2014 Enterprise Edition Core licenses and Software Assurance

2. Deploy an unlimited number of virtual machines

Microsoft SQL Server 2012

Reference: Microsoft SQL Server 2012 Licensing Guide

💡 Main changes comparing to previous version:

Core metric;

Core factor table introduced;

SQL Server Enterprise, per server, limited offer;

New edition SQL Server BI;

Minimum of 4 core licenses required for each physical processor;

Minimum of 4 core licenses required for each virtual machine

SQL Server 2012 commercial editions

Edition Server + CAL Per Core Requirements

Standard ✅* ✅ *SQL Server CALs

required

Business Intelligence ✅ 🚫 ㅤ

Enterprise 🚫 ✅ ㅤ

Parallel Data
Warehouse
🚫 ✅ ㅤ

Key capacity limits across SQL Server 2012 editions

Max Max Max Max

Max DB Max
Edition compute memory compute memory
Size DB Size
capacity utilization capacity utilization

Developer OS max OS max OS max OS max OS max OS max

4 GB
Lesser of 1 Lesser of 1
(Advanced
Express socket or 4 1 GB 10 GB socket or 4 N/A
Services
cores cores
Edition)

Web
Lesser of 1 64 GB 524 PB Lesser of 4 N/A 64 GB
 socket or 4 sockets or
cores 16 cores

Lesser of 4 Lesser of 4
Standard
socket or 16 64 GB 524 PB sockets or 64 GB 64 GB
(Core)
cores 16 cores

Business Lesser of 4
Intelligence socket or 16 64 GB 524 PB OS max OS max OS max
(Server + CAL) cores

Enterprise
OS max OS max 524 PB OS max OS max OS max
(Per Core)

Enterprise
20 core limit 12 TB 524 PB 20 core limit OS max OS max
(Server + CAL)

SQL Server 2012 Software Assurance

Benefit Description

Allows customers to run any number of instances of SQL Server

Unlimited Virtualization 2012 Enterprise Edition software in an
unlimited number of VMs. Applicable under the core licensing
model only.

Allows reassignment of SQL Server 2012 licenses within a server

License Mobility within a
farm more than once every 90 days. Does not apply to SQL
Server Farm
Server PDW.

License Mobility through Software Allows license reassignment of SQL Server 2012 to third party
Assurance shared servers. Does not apply to SQL Server PDW.

Allows backup instances of SQL Server 2012 software for

Cold Back Ups
temporary use in a server dedicated to disaster recovery.

Provides license grants and additional use terms for legacy SQL
Special Migration Offers Server 2008 R2 customers who are still migrating to current SQL
Server 2012 product editions and license models.

Allows access to new product features and functionality

SQL Server Appliance Updates between major appliance software releases. Applies to SQL
Server PDW deployments only.

In addition to the benefits noted above, Enrollment for

Additional Benefits for EAP Customers Application Platform (EAP) customers may also be eligible to
receive unlimited phone hours for problem resolution support.

SQL Server 2012 Licensing Model

A. SQL Server 2012 Per Core

To determine and acquire the correct number of core licenses needed, customers must:

1. Count the total number of physical cores in the server.

2. Minimum of four core licenses is required for each physical processor on a physical server.

3. To determine the total number of licenses required for the server.

 Multiply the number of cores by the appropriate core factor

Processor Type Core Factor

All processors not mentioned below 1

AMD Processors 31XX, 32XX, 33XX, 41XX, 42XX, 43XX, 61XX, 62XX, 63XX Series
Processors with 6 or more cores 0.75

Single-Core Processors 4

Dual-Core Processors 2

4. Core licenses are sold in packs of two, so customers must divide the number of licenses required by two to determine
the actual number of line items (licensing SKUs) to order.

When running SQL Server in a physical OSE, all physical cores on the server must be licensed. Software partitioning does
not reduce the number of core licenses required, except when licensing individual virtual machines (VMs). The minimum
number of licenses required for each processor on the server still applies.

A.1. Licensing individual SQL Server 2014 virtual machines

To license individual VMs using the Per Core model, customers must purchase a core license for each v-core (or virtual
processor, virtual CPU, virtual thread) allocated to the VM, subject to a four core license minimum per VM. For licensing
purposes, a v-core maps to a hardware thread. When licensing individual VMs, core factors do not apply.

1. License the virtual core in each virtual machine

2. There is a minimum of four core licenses required for each virtual machine

💡 Note: Licensing individual VMs is the only licensing option available for SQL Server 2014 Standard Edition
customers who are running the software in a virtualized environment under the Per Core model.

B. SQL Server 2014 Server + CAL

Under the Server+CAL licensing model, each operating system environment (OSE) running SQL Server 2014 software or
any of its components must have a SQL Server 2014 server license assigned to the physical server hosting the OSE. Each
server license allows customers to run any number of SQL Server instances in a single OSE, either physical or virtual.

💡 Notes

1. Running SQL Server software on different hardware partitions or blades requires separate software licenses.
Hardware partitions and blades are considered to be separate servers for licensing purposes and SQL Server
software licenses cannot be assigned to more than one server at any time.

2. To access a licensed SQL Server, each user or device must have a SQL Server CAL that is the same version or
newer than the SQL Server software version being accessed.

3. Devices not operated by humans require device CALs, even when connecting to SQL Server indirectly. For
human operated devices such as PCs or hand-held terminals, a user CAL or device CAL can be used.

4. While being version-specific, each SQL Server 2014 CAL provides access to any number of current and/or prior
version licensed SQL Server instances in a customer’s organization, regardless of the platform (32-bit, 64-bit or
IA64) or product edition, including legacy SQL Server Workgroup and SQL Server for Small Business edition
servers.
B.1. Licensing SQL Server 2014 individual virtual machines

To license individual VMs using the Server+CAL model (available for SQL Server 2014 Standard and Business Intelligence
editions only) customers simply purchase one server license for each VM running SQL Server software, regardless of the
number of virtual processors allocated to the VM.

💡 Note: Each user or device accessing SQL Server 2014 software, regardless of a virtual or physical deployment,
requires a SQL Server 2014 CAL.

C. Licensing SQL Server 2014 for maximum virtualisation

With SQL Server 2014 Enterprise Edition, customers who have licensed all physical cores on the server can run an unlimited
number of instances of the software in a number of OSEs (physical and/or virtual) equal to the number of core licenses
assigned to the server. For example, a four processor server with four cores per processor—fully licensed with sixteen core
licenses—can run SQL Server software in up to sixteen VMs, regardless of the number of virtual cores allocated to each
VM.

1. Fully license the server SQL Server 2014 Enterprise Edition Core licenses and Software Assurance

2. Deploy an unlimited number of virtual machines

Microsoft SQL Server 2008 R2

Reference: Microsoft SQL Server 2008 R2 Licensing Guide

SQL Server 2008 R2 commercial editions

Edition Server + CAL Per Processor Requirements

Web 🚫 ✅ ㅤ

Standard ✅* ✅ *SQL Server CALs

required

Enterprise ✅* ✅ *SQL Server CALs

required

Datacenter 🚫 ✅ ㅤ

Key capacity limits across SQL Server 2008 R2 editions

Max Max memory Max

Edition Max DB Size
compute capacity utilization OSEs Supported

Developer OS max OS max OS max 1

Express 1 CPU 1 GB 10 GB 1

Workgroup 2 4 GB 524 PB 1

Web 4 64 GB 524 PB 1

Standard 4 64 GB 524 PB 1
Enterprise 8 2 TB 524 PB 4

Datacenter OS max OS max 524 PB OS max

SQL Server 2008 R2 Software Assurance

Benefit Description

Move from previous version (e.g. SQL Server 2008) to current

Version Upgrade
version (e.g. SQL Server 2008 R2).

Deploy SQL Server 2008, 2005, or 2000 in place of currently-

Version Downgrade licensed version (per terms of Retail Software License Terms/
PUR).

Deploy lower edition in place of currently- licensed edition (per

Down Edition Rights
terms of Retail Software License Terms/PUR)

Move from lower edition (e.g. Standard) to higher edition (e.g.

Edition Step-Up
Enterprise)

SQL Server 2008 R2 Licensing Model

A. SQL Server 2008 R2 Per Processor

Microsoft offers a Per Processor licensing model to help alleviate complexity. When licensing SQL Server software under
the Per Processor model, you do not need to purchase additional CALs; it includes access for an unlimited number of users
or devices to connect from either inside or outside the firewall.

Per Processor Licenses for SQL Server 2008 R2 are available for Datacenter, Enterprise, Standard, Workgroup, Web, and
Parallel Data Warehouse editions.

💡 Notes
A Per Processor License is required for each processor installed on each operating system environment (OSE)
running SQL Server or any of its components (for example, Analysis Services);

For SQL Server running in physical operating system environments (POSEs), you must license all physical
processors;

Per Processor License costs are the same regardless of number of cores in the processor.

A.1. Licensing individual SQL Server 2008 R2 virtual machines

The number of operating system environments (OSEs) in which you may run instances of SQL Server 2008 R2 under the Per
Processor model depends upon the edition you license and whether or not you license all of the physical processors with a
Per Processor License.

B. SQL Server 2008 R2 Server + CAL

When licensing SQL Server software under the Server/CAL model, you purchase a Server License for the server and a
Client Access License (CAL) for each device (Device CAL) and/or user (User CAL) accessing or using the services or
functionality of SQL Server or any of its components (e.g. Reporting Services). A CAL is not software; it is a legal document
granting access.
 💡 Notes
SQL Server 2008 R2 CALs (or SQL Server 2008 CALs with SA) are required;

A given user or device only needs one SQL Server CAL to access any number of SQL Server instances in the
organization;

SQL Server CALs can also be used against any SQL Server regardless of the platform (32 bit, 64 bit, and IA64)
or edition (Workgroups, Standard, and Enterprise);

Use of hardware and/or software that reduces the number of devices or users that directly access or use the
software (multiplexing/pooling) does not reduce the number of CALs required;

Separate partitions or blades are considered to be separate servers for licensing purposes;

B.1. Licensing SQL Server 2008 R2 individual virtual machines

Edition Rule

Each Server License for SQL Server 2008 R2 Standard or Workgroup permits
Standard and Workgroup you to run the software in one (1) OSE (physical or virtual). Additional OSEs
require one (1) Server License each.

Each Server License for SQL Server 2008 R2 Enterprise permits you to run the
Enterprise Edition
software in up to four (4) OSEs (physical and/ or virtual).

ℹ️ SQL Server 2008 R2 CALs are required for any user or device accessing the SQL Server functionality or data,
regardless of whether SQL Server or any of its components are running in the physical or virtual OSE.

C. Licensing SQL Server 2008 R2 for maximum virtualisation

If you license all of the physical processors on the server (one license per physical processor), you may run unlimited
instances of the SQL Server software in the following number of OSEs (either physical or virtual):

Edition # of OSEs in Which You May Run SQL Server

SQL Server 2008 R2 Datacenter Unlimited

SQL Server 2008 R2 Enterprise Up to 4 per license

In the case of SQL Server 2008 R2 Standard, SQL Server 2008 R2 Workgroup, and SQL Server 2008 R2 Web, if you license
all of the physical processors you may run the software in the physical OSE only. In order to run the software in virtual
OSEs, you will need to license each virtual processor individually as described below.

The Licenseware Solution

Licenseware is the ideal solution for automating the technical license analysis and entitlements reconciliation for
Microsoft SQL Server. It can consolidate and analyse data from any data source as the relevant information is available in
the dataset. It’s compatible out of the box with all of the tools listed in the previous section (”Data Collection”).

Licenseware offers two modular applications that can be used independently or together for creating an end to end
Effective License Position:

Microsoft Deployment Manager (MDM): analyses the technical data and provides a comprehensive deployment report,
including scenario licensing for maximum virtualisation, flexibility or cost effectiveness.

Microsoft Entitlements Manager (MEM): analyses the license entitlement data from the standard Microsoft Licensing
Statement (MLS) and can be used in conjunction with MDM in order to reconcile the used licenses with the owned ones.

The MDM analysed deployment data is made available in a detailed report called “Microsoft SQL Server Details” which can
be used as is or exported in various formats (Excel, CSV, JSON).
If MEM is used together with MDM, it will generate the “Microsoft Effective License Position Report” which will reconcile
the deployed license requirements with the normalised entitlement information.

Feature List
This section describes the complete list of features associated to the Microsoft SQL Server analysis available in
Licenseware:

General Feature List

App Feature Description

Export data in multiple You can export the analysed data in Excel, CSV or
MDM / MEM
formats JSON.

You can create a public shareable (read only) link to

MDM / MEM Share Report your report to which you can assign an expiry period
(minutes, hours, days, etc.).

You can create custom reports with by choosing from

MDM / MEM Create Custom Report the available components, you can add supporting
notes.

You can create different project is you wish to

MDM / MEM Projects separate your data sets per business unit, cost center
and/or department.

You can invite individual collaborators and/or

MDM / MEM Collaboration
stakeholders to your projects.

Data Analysis Feature List

App Feature Description

MDM supports any data source or tool integration, via

static file upload or API integration, as long as the
dataset meets the minimum requirements for a
reliable license analysis.MDM supports out of the box
MDM / MEM Data Agnostic Ingestion all of the data sources described in the “Data
Collection” section. Any data source that is not yet
supported can be added on request in just a few days
by raising a support request and providing a small data
sample or the API specification.

Consolidation from Multiple MDM consolidates data from multiple data sources
MDM / MEM
Data Sources including data from file uploads and API.

Consolidation from Multiple MDM consolidates data from multiple data sources
MDM / MEM
Data Sources including data from file uploads and API.

MDM make the raw data available and gives the

option to edit the data based on new insights.

MDM / MEM Edit Raw Data

e.g. If the edition or CPU specifications changes on any
of your servers, you can edit the raw data and the
license calculation and report get updated in realtime.

With MDM you can create snapshots in time and

Create and Compare compare the different snapshots to understand how
MDM / MEM
Snapshots your infrastructure has changed from one snapshot to
another.

You can assign tags to different data uploads, in order

to differentiate the different types of environments /
MDM / MEM Tag data uploads
usage (e.g. finance department, production
environment, test, etc.).
 Does a global search based on one or multiple key
MDM / MEM Global Search
words.

Filter data based on one or multiple key words on a

MDM / MEM Filter Table Data
column basis. It allows for multiple filters at a time.

MDM / MEM Global Filter Applies global filter(s) to the entire report.

MDM / MEM Pivot Table Allows you to group data based on a given column.

Provides a report on all your data uploads, including

MDM / MEM History Report the data source and the status of each upload (e.g.
success/failed), including reason for failure.

License Analysis Feature List

App Feature Description

Installed Software Automatically recognises the installed software,

MDM Recognition and normalises the product name and enriches with
Normalisation product metadata.

Transparent Software Shows the raw software title and the recognised
MDM
Recognition Matching software match.

Recognises licensable components and assigns

MDM Component Recognition relevant licenses depending on edition match
Enterprise vs Standard.

Applies Core licensing rules by default, taking into

account core minimums and other relevant licensing
MDM Core License Calculations
rules (e.g. physical vs virtual, Standard vs Enterprise -
considering the no. of VMs running on a given host).

Applies relevant SA rules depending on licensing

scenario applied.
Software Assurance (SA)
MDM
Calculations e.g. max no. of virtual instances of SQL Server based
on the host server having Enterprise edition with or
without SA.

Maximum virtualisation with SQL Server Enterprise

MDM Scenario Licensing including/excluding Software Assurance (SA) vs SQL
Server Standard per instance.

Exclude Relevant
Ability to exclude DR, Dev, UAT, etc. environments
MDM Environments from License
from total license calculations.
Calculations

Calculates estimated licensing costs in USD, using the

MDM Price Est. Calculations
standard price list.

Provides actionable insights based on analysed data.

MDM Actionable Insights e.g. flags discontinued dates, trials/eval products,

CAL requirements, server installation on desktop
devices, etc.

Establishes a hierarchy of deployment and

Automated License entitlement value and automatically assigns them
MEM
Allocation logically to minimise compliance risk and maximise
surplus.

License Entitlement SKU Automatically normalises MLS SKU names with actual
MEM Recognition and product names and matches them with installed
Normalisation products.
Key Benefits
There are numerous benefits associated to leveraging Licenseware for managing Microsoft SQL Server licenses:

Benefits Description

Allows you to utilise multiple data sources, from within and

Data coverage and validity environment. This not only increases data coverage, but improves the
validity and trustworthiness of the results.

Leverage your existing data sources and tools, instead of deploying

additional solutions to collect the data you already have.
Time to value through
existing data sources
Save time and cost by shortcutting your software license management
process by jumping straight to analysis.

Identify accidental usage and fix issues before the become real
Reduce compliance risk
problems.

Identify potential cost savings by identifying cost saving opportunities

Maximise cost savings
and licensing based on the scenario that fits your IT strategy.

Split cost and license allocations by departments or other variables

Split costs by variables
allowing you to manage different environments separately.

Automate the tedious process of allocating the right and best licensees
Automated license allocation (depending on cost or flexibility concerns) with Licenseware’s smart
algorithms.

Scenario building Simulate different licensing scenarios for future deployments.

Licenseware allows you to create different projects where you can invite
Team collaboration and
individual team members or third parties taking into account the data in
separation of concerns
scope.

Get the answers you need, when you need them. Blazing fast analysis for
On-demand answers
thousands of devices in minutes.

Access to expert resources

Access to technical documentation and licensing white papers.
and documentation

Licenseware subscriptions include expert licensing advice and support in

Expert advice and support
extracting the

Free training and certification Licenseware subscriptions include free training and certifications for you
program and your team.

Case Studies

🔋
Case Study #1: Implementing SAM Practices for SQL Server Licensing
Compliance in a Mid-Sized Energy Company (” Contoso Energy”)

ℹ️ Contoso Energy is a fictitious name used for information security purposes.

Background
Contoso Energy, a mid-size energy company, faced challenges in managing its Microsoft SQL Server licenses. With a
growing IT infrastructure and lack of structured SAM practices, Contoso Energy struggled to maintain compliance and
optimise its software licensing costs.

Introduction of SAM Practices

To address these challenges, Contoso Energy initiated a project to introduce SAM practices. A dedicated SAM team was
established, responsible for developing policies, work standards, and implementing a SAM tool. The team's primary task
was to create an Effective License Position (ELP) report, which required detailed analysis of acquired software licenses and
an inventory of the software in use.

Discovery and Analysis

The first phase involved gathering data on purchased licenses and conducting a thorough inventory of the IT environment.
Contoso Energy didn’t have a SAM Solution in place yet, so they collected the required data from two existing IT tools:
Microsoft SCCM and Lansweeper and used a PowerCLI script to collect the virtualisation topology from VMware. This
allowed them to save time on the data collection part as the tools were already part of their IT stack they didn’t have to
deploy any agents. And by consolidating the data from the tools, they ensured they got maximum coverage over their
assets. Once the technical deployment data was collected, Contoso used Licenseware’s Microsoft Deployment Manager
app to analyse it.

The SAM team meticulously reviewed all purchased records using an updated Microsoft Licensing Statement (MLS) as a
base and performed an entitlement inventory reconciliation. They uploaded the validated MLS to Licenseware’s Microsoft
Entitlements Manager app and generated an Effective License Position (ELP) for SQL Server.

Initial Findings
The initial ELP report revealed a concerning scenario: Contoso Energy required more SQL Server licenses than it had
purchased. This negative compliance status was primarily due to the fact some Enterprise components were deployed
alongside Standard database instances, new deployments that had been done without corresponding license purchases (a
lack of procedures), and the fact CAL requirements had not been considered with multiplexing for a particular application
using SQL. Whilst the customer had a mixture of Core and Server + CAL licensing models, neither was sufficient to cover
the problem.

Compliance Year 1 Cost

5,000 employees
$323,599.20
1,237 CALs needed $261.60 per CAL w/ SA

36 cores of SQL Server Standard License w/ SA needed

$81,627.48
$4,534.86 per 2 core pack

16 cores of SQL Server Enterprise License w/ SA needed

$138,860.32
$17,357.54 per 2 core pack

Addressing the License Shortfall

The straightforward solution was to purchase additional licenses to cover the shortfall. However, the SAM team advocated
for a more strategic approach. They proposed analysing the company's resource usage patterns and processes to identify
solutions that are more cost-effective.

Datacentre Configuration and License Optimisation

Contoso’s datacentre comprised several hosts with varying configurations, from 16 to 48 physical cores. Clustering was
implemented along with vMotion, enhancing management automation, reliability, and availability. Virtual machines had
virtual cores assigned in the range of 8 to 16 virtual cores.

Proposing a Solution
The SAM team suggested a potential solution to reduce the required licenses by reducing the number of virtual cores
assigned to VMs running SQL Server Standard. This approach would capitalize on the fact most VMs were running at an
average of 25% capacity, and a minimum of 4 virtual cores for SQL server standard could be applied, reducing the
requirement in half for the selected virtual machines.

Next, they documented which devices had Enterprise licensable components deployed and set a project to investigate the
component usage and, if they were not in use, to be removed.
Lastly, utilising the now available core licenses, these were able to cover the shortfall on the SQL instance associated with
their payroll system and remove the requirements for additional CAL licenses, as all employees utilise this payroll system,
under the Server + CAL model it would have required all employees to have CALs which they did not have sufficient
available.

Evaluating Impact and Feasibility

Implementing this solution required careful consideration of its impact on the datacentre's configuration, database server
processing capacity, and the operation of production applications. Additionally to this investigation on the Enterprise
component utilization was required to understand if the functionality was actually required. The SAM team collaborated
with other departments, including procurement and IT, to assess the feasibility of this solution.

A steering committee comprising key stakeholders in IT service management was convened to deliberate on the proposed
changes. The primary question was whether reducing the cores assigned to particular virtual instances would adversely
affect the reliability and availability of company resources.

Decision and Outcome

After thorough analysis and discussions, the steering committee concluded that limiting virtual core assignments was
feasible without significantly compromising reliability or availability. This decision allowed Contoso Energy to rationalize
its SQL Server license consumption, reducing the number of required licenses to less than the acquired ones and ensuring
compliance without the immediate need for additional license purchases. Additionally to this it was determined the
licensable components were not, in fact, needed for operation and were decommissioned. They continued to renew their
Software Assurance on the surplus licenses to assign them in their Azure environment under Azure Hybrid Use Benefits,
where One core on-premises = One vCore in General Purpose Azure compute, resulting in a cost-saving on their Azure
subscription.

Conclusion
This case study demonstrates the critical role of SAM practices and leveraging the proper tooling in managing software
licenses, particularly for complex products like Microsoft SQL Server. By adopting a proactive and analytical approach,
Contoso Energy not only achieved compliance but also optimized its licensing strategy, highlighting the importance of
SAM in modern IT environments.

Case Study #2: Automated license allocation and optimisation

🚙
recommendations on SQL/Windows Server in a Large-Sized Manufacturing
Company (” Contoso Car Company”)

ℹ️ Contoso Car Company is a fictitious name used for information security purposes.

Background
Contoso Car Company, a large size enterprise specialized in manufacturing, had an issue in advising it’s subsidiaries of the
most optimal license allocations for both Windows Server and SQL Server. Whilst all subsidiaries reporting directly to the
parent company were responsible for their local license purchases, requirements, compliance, and allocations, they sought
advice from their parent specialists due to a lack of internal skill sets. The SAM team at the parent company, however, did
not have sufficient time to detail optimization strategies or compliance reporting multiple times throughout the year for
multiple bodies, therefore were after automation that could generate these insights for the wider organization to be
consumed at will.

Current tooling
Whilst Contoso Car Company had already implemented SAM tooling within their environment, it lacked the automated
allocation of licenses, alongside multiple scenarios on how to best optimize a given deployment, meaning manual
intervention was still required on top of their deployment and entitlement data. They wished for a solution that could take
data from their current tooling, including both deployment and entitlement data, and then surface the aforementioned
requirements via a SaaS portal to all relevant subsidiaries with relevant access controls. Assuming the stage 1 integration
went as expected, they wished for the entitlement allocation data to be pushed back to their current SAM tool via API to
update it accordingly once the subsidiary had approved the allocation.

Integration
Contoso Car Company's SAM tooling was already supported by Licenseware for analysis. However, they. wanted additional
data points to be included within the analysis so further data would be conducted afterward based on the likes of
geography, cost center, department, application owner, etc. These were not readily supported by Licenseware, so as part
of the Statement of Works, these additions were included to cater to these specific data points.

Initial Usage and Change Management

Upon successfully addressing the data integration requirements, a subset of subsidiaries were tasked to champion the
internal adoption of the solution. This was decided collectively by Contoso Car Company and Licenseware to ensure those
who sought comfort in relying on manual analysis conducted by a human had dedicated points of contact to reach out to if
they had any questions or doubts about the license allocations or recommendations. It was found that during the initial
tests by the selected champions, their license allocations suggested by the parent companies' specialists were very similar,
if not the same, as what Licenseware had recommended, providing confidence in the allocations and deployments. That
being said, once the program was scaled out globally, a number of subsidiaries were identified to have been procuring the
incorrect licenses based on their deployment requirements at a component level of SQL, causing a compliance issue where
some subsidiaries had a surplus, and some others lacked entitlement.

Addressing the License imbalance

As some subsidiaries had opposing ends of the compliance scale (surplus vs. shortfall), Contoso Car Company decided to
conduct an effective license position, including those business units in question, theorizing that they would counter-act
one another. Combining the data within Licenseware, this process was fairly straightforward, surfacing the fact that they
did, in fact, have an overall surplus of SQL core-based licenses that were being utilized for external (public) facing services;
below are the details:

Product Position Cost

SQL Server Standard 2 Core Pack SA Only +24 $12,828

SQL Server Standard 2022 2 Core Pack L/SA +16 $72,544

Conclusion
Whilst the parent company SAM team is still involved in some work with subsidiaries directly, a large amount of manual
work was removed via automated analysis, allowing them to focus on more strategic programs. Additionally, all business
units are able to obtain answers to their questions much faster via the Licenseware portal regarding their specific
Microsoft deployments and potential future scenarios. Lastly, even though Contoso Car Company chose to continue the
renewal of their SQL Server Core-based Software Assurance, they did so with upcoming projects in mind to cover the
licensing requirements, avoiding high costs in investing in License and Software assurance purchases in the future.

Conclusion
In the dynamic and data-centric business landscape of today, effective software asset management (SAM) is paramount.
As SQL Server continues to be a cornerstone for enterprise data management, understanding its complex licensing models
is crucial to optimizing costs and ensuring compliance. This white paper has explored the intricate nature of SQL Server
licensing, from the various editions and licensing models to common challenges and strategic solutions for cost
rationalization.

By highlighting the importance of strategic planning, entitlement analysis, and comprehensive deployment assessments,
this paper has provided actionable insights and best practices for maximizing the value of SQL Server investments. We
have delved into the specificities of SQL Server versions from 2008 to 2022, elucidating the benefits and nuances of each
licensing model.

Moreover, the case studies presented exemplify real-world applications of these strategies, demonstrating how
businesses like Contoso Energy and Contoso Car Company have successfully navigated licensing complexities and achieved
significant cost savings and compliance. These examples underscore the necessity of robust SAM practices and the value
of leveraging advanced tools like Licenseware's Microsoft Deployment Manager (MDM) and Microsoft Entitlements
Manager (MEM) to automate and optimize license management.

Licenseware stands out as a vital solution for organizations aiming to streamline their SQL Server license management. Its
modular, data-agnostic approach allows for seamless integration with existing IT tools, providing accurate, real-time
insights into licensing needs and opportunities for cost optimization. By automating technical license analysis and
entitlements reconciliation, Licenseware empowers businesses to make informed decisions, reduce compliance risks, and
maximize software investments.

In conclusion, effective SQL Server license management is not merely about compliance; it's about leveraging strategic
insights to drive business value. With the right tools and practices, organizations can turn the complexities of SQL Server
licensing into opportunities for optimization and growth. Licenseware is committed to supporting this journey, providing
the expertise and technology necessary to navigate the evolving landscape of software asset management successfully.

Call to Action
Are you ready to streamline your Microsoft SQL Server license management and maximize efficiency?

Discover the power of the Microsoft Deployment Manager (MDM) —an innovative app designed to simplify your
deployment analysis process and ensure you're fully leveraging your SQL Server environment while maintaining
compliance with your Microsoft contracts. Whether you're managing a few servers or orchestrating a complex enterprise
infrastructure, MDM provides the clarity and control you need for your SQL Server and Microsoft server environment.

Sign up today and experience first-hand how MDM can optimize your operations, reduce license costs, and manage
compliance risks. Don't let complexity slow you down. Embrace simplicity and efficiency with Microsoft Deployment
Manager and propel your business forward.

Start your journey to a more streamlined and effective IT environment now!

🎁 Use this discount code and get 10% off your plan: 🏷️ WHITEPAPER10

About Licenseware

Licenseware is a next generation SAM tool relies on highly

specialised, modular apps designed to solve specific issues
Get in touch of enterprise software license management. This
approach ensures that each module provides detailed

🤙 US: +1 (914) 600-3362 compliance analysis, optimisation recommendations, and

comprehensive audit capabilities. By focusing on specific
🤙 UK: +44 788 329 9357 vendors, and/or product groups, Licenseware delivers

✉️ [email protected] expert-level precision and efficiency. Organisations can

tailor their software asset management strategies with
these tools, achieving cost-effectiveness while maintaining
strict compliance. This modular system not only supports
scalability but also adapts seamlessly to the unique needs
of businesses, simplifying the complexities of license
management in modern IT environments.
🌐 www.licenseware.io
Appendices

A1. SQL Server Release and built numbers

Release Commercial
RTM built - no SP Details Editions & Metrics
Name

SQL Server 16
codename Dallas Enterprise – Per Core
SQL Server 2022 16.0.1000.6 Release date: 2022-11-16 Standard – Per Core
Support end date: 2028-01-11 Standard – Per Server CAL
Ext. end date: 2033-01-11

SQL Server 15
codename Aris Seattle Enterprise – Per Core
SQL Server 2019 15.0.2000.5 Release date: 2019-11-04 Standard – Per Core
Support end date: 2025-01-07 Standard – Per Server CAL
Ext. end date: 2030-01-08

SQL Server 14 Enterprise – Per Core

codename vNext Enterprise – Per Server CAL
SQL Server 2017 14.0.1000.169 Release date: 2017-10-02 (20 core limit)
Support end date: 2022-10-11 Standard – Per Core
Ext. end date: 2027-10-12 Standard – Per Server CAL

Enterprise – Per Core

SQL Server 13
Enterprise – Per Server CAL
Release date: 2016-06-01
SQL Server 2016 13.0.1601.5 (20 core limit)
Support end date: 2021-07-13
Standard – Per Core
Ext. end date: 2026-07-14
Standard – Per Server CAL

Enterprise – per Core

SQL Server 12 Enterprise – Per Server CAL
Release date: 2014-04-01 (20 core limit)
SQL Server 2014 12.0.2000.8
Support end date: 2019-07-09 Standard – per Server CAL
Ext. end date: 2024-07-09 Standard – per Core
BI – per Server CAL

Enterprise – per Core

SQL Server 11
Enterprise – Per Server CAL
codename Denali
(20 core limit)
SQL Server 2012 11.0.2100.60 Release date: 2012-03-06
Standard – per Server CAL
Support end date: 2017-07-11
Standard – per Core
Ext. end date: 2022-07-12
BI – per Server CAL

SQL Server 10.5 Datacenter – per Processor

codename Kilimanjaro Enterprise – per Processor
SQL Server 2008 R2 10.50.1600.1 Release date: 2010-04-21 Enterprise – Per Server CAL
Support end date: 2014-07-08 Standard – per Server CAL
Ext. end date: 2019-07-09 Standard – per Processor

SQL Server 10
Enterprise – per Processor
codename Katmai
Enterprise – Per Server CAL
SQL Server 2008 10.0.1600.22 Release date: 2008-08-07
Standard – per Server CAL
Support end date: 2014-07-08
Standard – per Processor
Ext. end date: 2019-07-09

SQL Server 9 codename Yukon Enterprise – Per Processor

Release date: 2005-11-07 Enterprise – Per Server CAL
SQL Server 2005 9.0.1399.6
Support end date: 2011-04-12 Standard – Per Server CAL
Ext. end date: 2016-04-12 Standard – Per Processor

SQL Server 8 codename Shiloh Enterprise – Per Processor

Release date: 2000-11-30 Enterprise – Per Server CAL
SQL Server 2000 8.00.194
Support end date: 2008-04-08 Standard – Per Server CAL
Ext. end date: 2013-04-09 Standard – Per Processor
Glossary
Term Definition

A server is a physical hardware system capable of running server software. A

Physical server hardware partition or blade is considered to be a separate physical hardware
system.

A processor is generally a physical chip that resides in a physical socket of the

Physical processor
hardware partition and contains one or more cores.

Each physical processor contains smaller processing units called physical cores.
Physical core
Some processors have two cores, some four, some six or eight, and so on.

Virtual core A virtual core is a virtual representation of one or more hardware threads.

A hardware thread is either a physical core or a hyper-thread in a physical

Hardware thread
processor.

Physical Operating
A physical operating system environment (OSE) is configured to run directly on a
System Environment
physical hardware system and is all or part of an operating system instance.
(POSE)

Delivers fully featured database capabilities for mid-tier applications and data
Standard Edition
marts.

For applications requiring mission critical in-memory performance, security and

Enterprise Edition
high availability.

A license that allows a client device or user to connect to a server running

CAL (Client Access
Microsoft software. CALs are typically required for products like Windows Server
License)
and SQL Server.

A licensing model where the cost is based on the number of cores in the server's
Per Core Licensing
processor. Each physical core in the server must be licensed.

A licensing model where the server is licensed with a Server License, and each
Server + CAL Licensing
user or device accessing the server requires a Client Access License (CAL).

A benefit available to customers with Software Assurance, allowing them to move

License Mobility
certain server application licenses to the cloud or across different servers.

A Microsoft maintenance program that provides benefits like version upgrades,

Software Assurance
deployment planning, and additional training for licensed software.

A standby server that is used to take over operations in case the primary server
Failover Server fails. SQL Server licensing rules often allow for a failover server without
additional licensing.

A system design protocol and associated implementation that ensures a certain

High Availability
degree of operational continuity during a given measurement period.

A set of policies, tools, and procedures to enable the recovery or continuation of

Disaster Recovery vital technology infrastructure and systems following a natural or human-induced
disaster.

A software emulation of a physical computer, running an operating system and

Virtual Machine (VM)
applications just like a physical computer.

Virtual Operating
An operating system environment that is virtualized. Each VOSE is a separate
System Environment
instance of an operating system running in a virtual machine.
(VOSE)

A specific individual authorized to access a licensed software application, as

Named User opposed to a concurrent user which can be any individual using the software at a
given time.

A server that is not running active SQL Server workloads but is ready to take over
Passive Server
in case of a failover scenario.
 A multiplier used in calculating the number of licenses required for a server,
Core Factor based on the number and type of processors used. The core factor varies by
processor type.

The process of upgrading from a lower SQL Server edition to a higher one (e.g.,
Edition Upgrade
Standard to Enterprise), typically requiring additional licensing costs.

The methodology or system used by a software vendor to determine how

Licensing Model
software is licensed and priced.

The minimal installation option for the Windows Server operating system that
Server Core
provides a low-maintenance environment with limited functionality.

Software that creates and runs virtual machines, enabling multiple operating
Hypervisor
systems to share a single hardware host.

Adherence to the licensing terms and conditions set forth by the software
Licensing Compliance
vendor, ensuring that all software usage is properly licensed.

The number of virtual machines running on a single physical server. Higher VM

VM Density
density can impact licensing requirements and costs.

A computing environment that combines on-premises, private cloud, and public

Hybrid Cloud
cloud services with orchestration between them.

A processor allocated to a virtual machine by the hypervisor. It can map to a

Virtual Processor
physical core or a hardware thread.

The core service for storing, processing, and securing data. Provides controlled
Database Engine
access and rapid transaction processing.

The specific parameters and measurements used to determine the licensing

Licensing Metrics
requirements for software usage.

The entitlements provided by a software license that dictate how many virtual
Virtualization Rights
machines can be created and run on a physical server.

A single installation of SQL Server, which can include multiple databases and
Instance
server objects.

A pre-defined set of server-wide privileges assigned to a user or group of users to

Server Role
control access and administration of the SQL Server.

A model that requires purchasing licenses for the total number of cores on the
Core Licensing
server, often with a minimum number of licenses per server.

Unlimited A licensing benefit that allows unlimited virtual instances of SQL Server on a
Virtualization server, typically available with the Enterprise Edition and Software Assurance.

The process of transferring a software license from one server to another, subject
License Reassignment
to vendor policies and conditions.

The main server in a failover setup that actively runs SQL Server workloads and
Primary Server
handles client requests.

A licensing model where software is purchased through a time-limited

Subscription Licensing subscription, typically providing access to updates and support during the
subscription period.

Core Entitlement The number of cores that are licensed and can legally run SQL Server instances.

The binding of a specific process or task to a specific processor or core, used to

Processor Affinity
optimize performance.

A feature that allows the allocation of memory resources to virtual machines

Dynamic Memory
based on their current needs, optimizing the use of available memory.

A feature that enables the management of SQL Server workload and system
Resource Governor
resource consumption by specifying limits on resource usage.
 The simultaneous processing of multiple tasks or threads, enhancing
Parallel Processing
performance and efficiency in multi-core processors.

The process of reducing the number of servers or server locations by combining

Server Consolidation
workloads onto fewer machines, often through virtualization.

License Mobility
A benefit that allows licenses to be reassigned to shared cloud infrastructure,
through Software
providing flexibility in deploying workloads across different environments.
Assurance

Self-Service Business Tools and technologies that enable end-users to access, analyze, and visualize
Intelligence (BI) data without needing deep technical knowledge.

A system used for reporting and data analysis, centralizing and consolidating
Data Warehouse
large amounts of data from multiple sources.

Extremely large datasets that require advanced methods and technologies for
Big Data
storage, processing, and analysis.

The process of enhancing the performance of SQL queries by selecting the most
Query Optimization
efficient execution plan.

An index that determines the physical order of data in a table and allows efficient
Clustered Index
retrieval of records based on the indexed column(s).

An index that creates a logical ordering of data separate from the physical order,
Non-Clustered Index
allowing faster searches on non-primary key columns.

The process of copying and distributing data and database objects from one
Replication
database to another and synchronizing between databases for consistency.

FAQ
What are the differences in licensing SQL Server with or without Software Assurance?
Here's a side-by-side comparison highlighting the differences between SQL Server licensing with and without Software
Assurance:

SQL Server
SQL Server
(Without
Feature (With Software
Software
Assurance)
Assurance)

Licensing Core-based and Core-based and

Model Server/CAL Server/CAL

Core-Based Must license all Must license all

Licensing physical cores physical cores

Minimum Core
4 core licenses 4 core licenses
Licenses per
(2 per core) (2 per core)
Server

Can license the

Must license physical host
Virtual
each VM and cover all
Machine Rights
individually VMs on that
host

Allows for one

passive failover
High No additional
instance per
Availability failover rights
licensed SQL
Server
 Allows license
mobility across
License Limited license
servers in the
Mobility mobility
same server
farm

VMs can be
Virtual VMs must be moved freely
Machine reassigned across servers
Mobility within 90 days in the same
server farm

Access to new
No access to versions and
Access to New
new versions or features during
Versions
features the agreement
period

Allows use of
Hybrid Use licenses on-
Not available
Benefit premises and in
the cloud

Flexibility in
Must license all
managing
Compliance physical cores
licenses and
Requirements and individual
moving VMs
VMs accurately
across servers

Without
Software
Assurance: With Software
Licensing all 16 Assurance:
cores covers the Licensing all 16
physical host cores covers the
but requires physical host
Example individual and allows
Scenario (16- licensing for running any
core server) each VM if number of VMs.
more than 16 Added benefits
cores are include failover
needed. To run rights and
4 VMs, each mobility for
with 4 cores, VMs.
you need 16
core licenses.

What is Microsoft license compliance verification (commonly known as “audit”)?

Microsoft license compliance verification (commonly known as “audit”) is a formal, mandatory compliance review of a
company's use of Microsoft products and services, and it is part of the Microsoft license and contract compliance program.
Microsoft conducts industry-standard compliance reviews with its business customers through an independent auditor
pursuant to the terms of their agreement. This review is an effort to help customers achieve and maintain license
compliance, and to protect Microsoft intellectual property rights. Therefore, be assured that unless Microsoft invokes its
contractual right to verify compliance via a third-party accounting firm (as fully documented in your Volume Licensing
Agreement), you are not involved in a license compliance verification.

Source: ‣

What is Microsoft Software Asset Management (SAM)?

The Microsoft SAM program is a trusted IT advisory service based on industry SAM standards that help customers gain
data insights, optimize licensing, minimize risks, and be more productive with their IT investments. SAM engagements
provide a 360-degree view of the customer's IT infrastructure and a set of recommendations on ways to improve their
overall asset management, license management, and SAM policies and procedures. With this comprehensive view,
customers get valuable recommendations on areas that are most challenging for their business. SAM engagements are
performed by Microsoft SAM Certified Partners and are voluntary. We believe that SAM can be a strategic advantage for
all our customers. Learn from customers how SAM has benefited their business.

Source: ‣

Some sources claim that Microsoft Software Asset Management (SAM) and license
compliance verification (commonly known as “audit”) are the same. Is this correct?
No, Microsoft SAM and license compliance verification are not the same. The list below shows the differentiation between
SAM and license compliance verification.

1. Microsoft Software Asset Management (SAM)

Nature of engagement - Voluntary

Performed by - Microsoft SAM Certified Partners with more flexibility in process

Objective - Help customers maximize value, minimize risks, and achieve more with their IT investment

2. Microsoft license compliance verification (audit)

Nature of engagement - Mandatory contractual requirement

Performed by - Independent, internationally recognized certified public accounting firms. However, in some
jurisdictions, verifications are also conducted by authorized consultants on behalf of Microsoft.

Objective - Help customers achieve and maintain license compliance, and to protect Microsoft’s intellectual property
rights

Source: ‣

How does Microsoft select customers for license compliance verifications?

Microsoft uses a programmatic approach to select customers for license compliance verification. Any customer with a
Microsoft volume license may be selected. Microsoft performs license compliance verifications with a limited number of
customers each year, to verify customers’ compliance to the terms and conditions of their respective agreements with
Microsoft.

Source: ‣

How can customers prepare for Microsoft license compliance verifications?

A Microsoft license compliance verification is a routine process of checking customers’ compliance with Microsoft licensing
agreements. Customers who take licensing compliance seriously and have a robust internal Software Asset Management
(SAM) process are likely to be better prepared for license compliance verifications. Learn how to establish an effective
SAM program.

Source: ‣

What should customers expect from a Microsoft license compliance verification?

Microsoft will directly provide customers with a formal notification of license compliance verification. The length of an
engagement varies based on the complexity of the IT environment of an organization. Per the customer's agreement,
Microsoft makes every effort to ensure minimal disruption of the customer's day-to-day operations.

Source: ‣

Who performs Microsoft license compliance verifications?

Microsoft license compliance verifications are executed by independent, internationally recognized certified public
accounting firms. However, in some jurisdictions, verifications are also conducted by authorized consultants on behalf of
Microsoft.

Source: ‣
What if license compliance verifications reveal license compliance issues?
The remedies and other requirements in case of compliance issue occurs are documented in your Volume License
Agreements (refer the clause on Compliance Verification). If you need additional clarification, contact your Microsoft
Account Manager.

Source: ‣

What are the licensing options for SQL Server in a hosting environment?
SQL Server can be licensed through either the Pay-As-You-Go (PAYG) model or the Bring-Your-Own-License (BYOL)
model:

PAYG: The end-client rents SQL Server licenses through the Service Provider License Agreement (SPLA) on a monthly
basis.

BYOL: The end-client brings their existing SQL Server licenses to the hosting provider, provided these licenses have
Software Assurance or are subscription-based.

What is the difference between SPLA and BYOL licensing for SQL Server?
SPLA: This is a monthly subscription model where the service provider licenses SQL Server on behalf of the client, and
the cost is included in the service fee.

BYOL: In this model, the client brings their own SQL Server licenses to the hosting provider, which must be eligible for
hosting under the terms of Software Assurance or subscription licensing.

Can I use my existing licenses with a hosting provider?

Yes, you can use your existing SQL Server licenses with a hosting provider if they are covered by Software Assurance or are
subscription licenses, and the hosting provider allows BYOL.

How do I avoid overpaying for SQL Server licenses?

To avoid overpaying:

Choose the most suitable licensing model for your needs.

Use mixed licensing (combining BYOL and SPLA) to handle both constant and seasonal demands.

Take advantage of cluster discounts and disaster recovery rights to optimize costs.

What common mistakes should be avoided when reporting SQL Server licenses in SPLA?
Avoid the following common mistakes:

Reporting incorrect license types or editions.

Not meeting the minimum requirement of four core licenses per VM or physical CPU.

Failing to report all authorized users when using Subscriber Access Licenses (SAL).

What are the different editions of SQL Server?

SQL Server is available in several editions:

Standard Edition: Suitable for small to medium-sized businesses requiring essential database functionalities.

Enterprise Edition: Designed for large enterprises needing high performance, scalability, and advanced features.

Web Edition: Available only through SPLA, intended for web hosting scenarios.

What are the licensing options for SQL Server Standard in SPLA?
SQL Server Standard in SPLA can be licensed:

Per core: For environments where user/device counting is impractical.

Per user or device: With Subscriber Access Licenses (SAL), which do not require server licenses.

What are the licensing options for SQL Server Enterprise in SPLA?
SQL Server Enterprise can be licensed:

Per virtual machine core: For flexible, virtualized environments.

At the physical host level: Allowing unlimited virtualization on a host, provided all physical cores are licensed.

What is the minimum number of core licenses required for a SQL Server virtual machine?
A SQL Server virtual machine requires a minimum of four core licenses, regardless of the actual number of virtual cores
used.

How do I choose the suitable SQL Server licensing model for my hosting environment?
Selecting the appropriate licensing model depends on several factors:

The SQL Server edition (Standard, Enterprise, Web).

The chosen licensing model (per-core, per user/device).

The specific requirements of your environment, such as the number of virtual cores, users, or devices. Consulting with a
licensing expert can help determine the most cost-effective and compliant model for your business.

What are the permitted periods of use for a disaster recovery server running SQL Server
under disaster recovery rights?
A disaster recovery server can be used during:

Brief disaster recovery testing within one week every 90 days.

Actual disaster periods when the primary production server is down.

Brief periods to facilitate the transition between the primary and disaster recovery servers.
Note: The disaster recovery server must not be in the same cluster as the primary production server.

What are the advantages of using the Pay-As-You-Go (PAYG) model for SQL Server licensing?
The PAYG model offers several benefits:

No long-term commitment: Licenses are billed on a monthly basis, allowing for flexibility.

Scalability: Easily adjust licensing to match changing workload demands.

Provider-managed: The hosting provider manages the licenses, reducing administrative overhead for the client.

What are the drawbacks of the Pay-As-You-Go (PAYG) model for SQL Server licensing?
While convenient, PAYG has some drawbacks:

No price protection: Monthly costs can increase, typically on an annual basis.

Potentially higher costs: PAYG can be more expensive over the long term compared to other licensing models.

What are the advantages of the Bring-Your-Own-License (BYOL) model for SQL Server
licensing?
BYOL provides several benefits:
 Cost savings: Utilize existing licenses, which can be more economical than SPLA.

Price protection: Licenses acquired through long-term agreements often include price protection.

Flexibility: Combine BYOL with SPLA to optimize costs for consistent and fluctuating workloads.

What are the drawbacks of the Bring-Your-Own-License (BYOL) model for SQL Server
licensing?
The BYOL model has some limitations:

Management overhead: Clients must manage their own licenses and ensure compliance.

Eligibility: Only licenses with Software Assurance or subscription-based licenses are eligible.

Provider restrictions: Not all hosting providers support BYOL.

How do SQL Server licensing requirements differ between physical and virtual environments?
Physical environments: Licenses are required for each physical core in the server, with a minimum of four core licenses
per physical CPU.

Virtual environments: Licenses are required for each virtual core in the virtual machine, with a minimum of four core
licenses per virtual machine.

What is the Flexible Virtualization Benefit, and how does it apply to SQL Server licensing?
The Flexible Virtualization Benefit allows clients with Software Assurance or subscription licenses to use their licenses in
virtualized environments across any service provider's data center. This benefit enhances flexibility and cost-efficiency in
deploying SQL Server across different hosting environments.

Can I use SQL Server licenses without Software Assurance in a hosting environment?
No, to use SQL Server licenses in a hosting environment, they must be covered by active Software Assurance or be
subscription-based. This ensures compliance with Microsoft's licensing terms and eligibility for the Flexible Virtualization
Benefit.

What is the difference between SQL Server Standard and Enterprise editions in terms of
functionality and licensing?
SQL Server Standard: Suitable for small to medium-sized businesses, offering core database capabilities.

SQL Server Enterprise: Designed for large enterprises, providing advanced features such as high availability, extensive
security, and superior performance. Licensing costs are higher due to the additional functionalities.

How do I handle SQL Server licensing for disaster recovery setups?

For disaster recovery, the following licensing considerations apply:

Passive node discount: For each licensed active node, one passive node is free.

Disaster recovery server usage: Permitted for brief testing periods, during actual disasters, and for transition
assistance, but not within the same cluster as the primary server.

What tools or practices can help with accurate license reporting and management for SQL
Server in SPLA?
Effective license management involves:

Regular audits: Conduct frequent license audits to ensure compliance and avoid penalties.

Dedicated SPLA tools: Use specialized software tools to track and manage licenses accurately.
 Detailed documentation: Maintain comprehensive records of all licenses, usage, and reporting to streamline
compliance processes.

How do Subscriber Access Licenses (SAL) work in SPLA for SQL Server Standard?
Per-user/device licensing: Each user or device accessing the server requires a SAL.

Unlimited instances: No server licenses are needed, and there is no limit on the number of SQL Server instances
deployed.

What are the reporting requirements for SQL Server licenses under SPLA?
Service providers must:

Monthly reporting: Accurately report the usage of SQL Server licenses each month.

Compliance: Ensure all licenses, including SALs, meet the minimum requirements and are correctly reported to avoid
financial or legal repercussions.