SQL Server: Reference
Refer to the information below for descriptions of indicators and table columns on the SQL Server page.
Savings indicators
Indicator | Description |
---|---|
Potential savings | The estimated amount of potential monthly savings in licensing costs if all Eligible resources are converted to BYOL. |
Realized savings | The estimated amount you save in a month on licensing costs from resources that are BYOL-configured. |
BYOL coverage |
|
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 .
Indicator | Description |
---|---|
Available core licenses from SAM on Snow Atlas | The total number of available core licenses that are applicable for BYOL. |
Core license shortfall/excess | This indicator will have one of the following labels depending on your rate of coverage:
|
BYOL license status |
|
Resource table
Column | Description |
---|---|
Resource name | The user-created name of the resource. |
Resource ID | The unique identifier assigned to the resource by the cloud provider. |
Resource type | The type of resource. Only SQL Server resources are shown in the table. These resources include:
|
vCPU | The 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 required | The 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 model | The 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 tier | The compute tier the resource is assigned to. A compute tier is a pre-configured bundle of compute resources provisioned for different user needs. |
Service tier | The 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 ID | The unique identifier for the cloud subscription that contains the resource. |
Subscription name | The name of the subscription account that contains the resource. |
Date created (UTC) | The date and time the resource was created in UTC. |
License status | The license status of the resource's operating system.
|
Resource group | The logical container the resource is grouped within in the cloud providers' portal. |
Cloud provider | The cloud provider that hosts the resource. |
Region | The geographical location where the resource is hosted. |
Connector name | The unique identifier of the cloud connector used to fetch the resource data. |