Skip to main content

Example: Microsoft SQL Server 2019 Standard

The following example describes a licensing scenario of a virtual machine (VM) with an installation of the Microsoft SQL Server 2019 Standard application. To cover an installation on the VM, we need a license with active Software Assurance.

In the compliance summary of the application Microsoft SQL Server 2019 Standard (the blue box) we see that:

  • The metric of the application is set to Number of processor cores.
  • There are no (0) licenses with that metric for this application.
  • There is a license requirement of 56 licenses.
  • There are 30 cores.
  • We are 48 licenses short.

ComplExMSSQL2019-Std_1

In the Details view of the Compliance tab, we see that there are no licenses registered for the metric of the application (the top red box), but there is a license available with an additional metric (the bottom red box):

  • There is 1 license available with the metric Installations.
    The initial requirement of 56 cores corresponds to 6 installations.

Default metric​

The initial license requirement of the application is 30 Cores. However, adjustments are made for SQL Server VM (8 licenses) and Minimum requirement (18 licenses) which result in a final requirement of 56 Required licenses.

ComplExMSSQL2019-Std_2

For information on the consumers of this application:

  • Click the Licenses tab, and then click Tracking.
    A list of all consumers that require a license is shown.

Adjustment for SQL Server VM​

An adjustment has been made for a VM that has hyper-threading enabled. In the Tracking view, the involved consumer has Entitlement state set to Not covered.

For detailed information:

  • On the Licenses tab and in the Tracking view, click the arrow next to the Required number of licenses (in this example 16).
    In the License requirements box, the SQL Server VM adjustment appears.

ComplExMSSQL2019-Std_3

For a virtual machine that is running Microsoft SQL Server and has hyper-threading enabled, the license requirement is equal to the number of logical processors. When we look at the consumer, we see that it has 16 logical processors and therefore we have a requirement of 16 licenses.

ComplExMSSQL2019-Std_8

Adjustment for Minimum requirement​

The setting Minimum number of licenses means that each consumer of the application must be covered with a certain number of licenses. When this setting is used, the set value is shown on the Information tab in application details.

ComplExMSSQL2019-Std_4

EXAMPLE

The Minimum number of licenses is adjusted to 8 cores by overriding the minimum requirement setting on the application level. For a consumer with 4 cores this will result in an additional adjustment of 4 cores to meet the minimum requirement of 8 cores.

For information on any adjustments that have been made for a consumer:

  • On the Licenses tab and in the Tracking view, click the arrow next to the number of Required licenses.
    In the License requirements box, any adjustments are shown.

ComplExMSSQL2019-Std_5

Other metrics​

On the Compliance tab and in the Details view, we see that we have a license available with an additional metric. In this case, a license with the metric Installations has been transferred from another version of the application via upgrade rights. For information on which version, click the Licenses tab, and then click Transfers.

ComplExMSSQL2019-Std_6

Since the metric of the application is set to Number of processor cores, each license of an additional metric must be translated into the metric of the application. In this case, the Installations license is translated into a corresponding 8 Cores license and is used for coverage of the application. This is indicated by the Licensing other metrics row in the section of the additional metric, and the Covered by other metrics row in the default metric section.

Default metrics without SA​

To cover a VM with an installation of the Microsoft SQL Server 2019 Standard application, you need a license with active Software Assurance (SA). In the example below, we try to cover a license requirement of 8 licenses with a license purchase without active SA. In License details, on the Assignment tab, we then see the message No active software assurance for the VM. The VM is not covered.

ComplExMSSQL2019-Std_7