Skip to main content

SQL Server: Reference

Refer to the information below for descriptions of indicators and table columns on the SQL Server page.

Savings indicators

IndicatorDescription
Potential savingsThe estimated amount of potential monthly savings in licensing costs if all Eligible resources are converted to BYOL.
Realized savingsThe estimated amount you save in a month on licensing costs from resources that are BYOL-configured.
BYOL coverage
  • Coverage rate: The percentage of eligible resources that use a BYOL licensing model. Resources with a License status of Not applicable are excluded from this value.
  • BYOL: The number of BYOL-configured resources.
  • Eligible: The number of resources eligible to be converted to a BYOL licensing model.

Licenses indicators

The Licenses indicators are supported by licensing data from SAM on Snow Atlas.

These indicators represent the count of normalized core licenses, where one Enterprise license is equivalent to four Standard licenses. The total license counts shown in these indicators take into account that license requirements vary depending on the type of resource. For more information on license requirements, see How licenses apply to Azure resources .

IndicatorDescription
Available core licenses from SAM on Snow AtlasThe total number of available core licenses that are applicable for BYOL.
Core license shortfall/excessThis indicator will have one of the following labels depending on your rate of coverage:
  • Core license shortfall: You do not have the required number of core licenses for your resources with a BYOL license status. Additional licenses must be acquired, or you must disable BYOL resources to eliminate the deficit.
  • Core license excess: You have complete license coverage for your resources with a BYOL license status, and additional licenses that can be applied to eligible resources.
BYOL license status
  • Required: The total number of core licenses required for your resources with a BYOL license status.
  • Available: The total number of available core licenses that are applicable for BYOL.
  • Shortfall: This value is only represented in the chart if you do not have the required number of core licenses for your resources with a BYOL license status.

Resource table

ColumnDescription
Resource nameThe user-created name of the resource.
Power stateThe power state of the SQL Server resource. Power states affect license requirements and costs. The power state can be:
  • On: A resource that is powered on. A BYOL-enabled resource with this power state requires licenses, and a pay-as-you-go resource will incur a licensing cost.
  • Off: A resource that is stopped (or in the case of SQL Virtual Machine, the resource is deallocated). A BYOL-enabled resource with this power state does not require licenses, and a pay-as-you-go resource will not incur a licensing cost.
  • Off (license req): A BYOL-enabled resource that is stopped, but still requires licenses.
  • Unknown: An error has occurred while fetching resource data. To ensure you remain compliant with Microsoft's terms, Cloud license management assumes that resources with this power state require licenses if they are BYOL-enabled, and that they will incur licensing costs if they are pay-as-you-go.
The Cloud license management savings and license indicators only consider resources that have the power state On, Off (license req) and Unknown.
Resource IDThe unique identifier assigned to the resource by the cloud provider.
Resource typeThe type of resource. Only SQL Server resources are shown in the table. These resources include:
  • SQL Server on Azure VM (SqlVirtualMachine)
  • Azure SQL Managed Instance (SqlManagedInstance)
  • Azure SQL Database (SqlDatabase)
  • Azure Elastic Pool (SqlElasticPool)
Tip: If you select the name of a single resource from the resources tables, an information panel will display the license requirements for the resource and its current Azure Hybrid Benefit license status; it will also display a detailed summary of the resource.
vCPUThe number of vCPUs assigned to the resource. This column will be blank for resources with a License status of Not Applicable, or when the vCPU count cannot be calculated.
For instances with constrained vCPU, this column reflects only the number of active vCPUs. This is because, unlike Windows Server licensing, SQL Server licenses are only required for active vCPUs. For more information on constrained vCPU, see Constrained vCPU sizes for database workloads .
Licenses requiredThe number of SQL Server licenses required for the resource to qualify for Azure Hybrid Benefit. SQL Server Enterprise and Standard core licenses with Software Assurance qualify, as do SQL Server core license subscriptions. One SQL Server Enterprise license has the same coverage as four Standard licenses.
The number of licenses required differs depending on the type of resource. For more information, see How licenses apply to Azure resources .
Purchase modelThe pricing model used to purchase the SQL Server license.
For information on the differences between a vCore-based purchasing model and a DTU-based purchasing model, see Purchasing models - Azure SQL Database .
Compute tierThe compute tier the resource is assigned to.
A compute tier is a pre-configured bundle of compute resources provisioned for different user needs.
Service tierThe service tier the resource is assigned to.
A service tier is a model of pre-configured performance and security capabilities provisioned for different user needs.
Savings (USD)The estimated monthly amount you save in licensing costs with BYOL. This column will display a Realized savings value for resources that have already migrated to BYOL. A Potential savings value will dislay for BYOL-eligible resources.
Subscription IDThe unique identifier for the cloud subscription that contains the resource.
Subscription nameThe name of the subscription account that contains the resource.
Date created (UTC)The date and time the resource was created in UTC.
License statusThe license status of the resource's operating system.
  • BYOL: The license is BYOL-configured.
  • Eligible: The license is not BYOL-configured, but is eligible for conversion.
  • Not applicable: The license is ineligible for BYOL. The SQL resource configurations that are ineligible include: Single vCore Serverless, Single DTU, Elastic Pool vCore, Elastic Pool DTU.
Resource groupThe logical container the resource is grouped within in the cloud providers' portal.
Cloud providerThe cloud provider that hosts the resource.
RegionThe geographical location where the resource is hosted.
Connector nameThe unique identifier of the cloud connector used to fetch the resource data.