Manage licensing and billing of SQL Server enabled by Azure Arc
This article explains how to manage licensing and billing of SQL Server enabled by Azure Arc. Only the core-based licensing methods are directly supported by SQL Server enabled by Azure Arc. For information about how you can manage SQL Server instances with a Server+CAL license, see Manage SQL Server instances with a Server+CAL license. The full range of the licensing options is described in the SQL Server Licensing Guide.
Licensing and billing in production environment
You can use one of the three licensing options.
-
Use Enterprise or Standard license for the vCPUs (v-cores) of the virtual machine that runs one or multiple instances of SQL Server. Each virtual machine is billed individually for the v-core allocated to it. The following diagram illustrates this licensing method and shows its cost implications.
License by physical cores without virtual machines option
Use Enterprise or Standard Edition license for the physical cores (p-cores) of the host that runs one or multiple instances of SQL installed directly on the host without using VMs. Each instance has access to all p-cores supported by the installed edition limits up to all p-cores of the host. Regardless of the instance limits though, the host is billed for all the p-cores based on the highest SQL Server edition installed on it. For details, review Compute capacity limits by edition.
The following diagram illustrates the cost implications of deploying two standard edition instances on a physical host without using VMs.
License by physical cores with unlimited virtualization
Use Enterprise Edition license for the physical cores (p-cores) of the host that runs any number of virtual machines with any number of instances of SQL Server. A single p-core license is a separate Azure resource representing all licensed p-cores and is billed independently. The following diagram illustrates the cost implications of licensing a physical host and using unlimited virtualization.
Note
Normalized cores (NC) are used to illustrate the cost implications of different licensing options. One Standard Edition core license is an equivalent of one NC. One Enterprise Edition core license is an equivalent of four NCs. For more information, see How licenses apply to Azure resources.
For each of these options, you have to decide how you want to pay for the license. The following table shows your payment options.
Payment option | V-core licensing | P-core licensing without VMs | P-core licensing with unlimited virtualization |
---|---|---|---|
Subscribe to the service through Microsoft Azure using a pay-as-you-go method | Yes | Yes | Yes |
Bring your own license with SA or SQL subscription1 | Yes | Yes | Yes |
Bring your own license without SA2 | Yes | Yes | No |
1 You already have a license with active Software Assurance or an active SQL subscription.
2 You own a perpetual license or use a Server+CAL license.
Note
Your choice of payment options above may impact your outsourcing options. For more information, please see Product Terms and Flexible Virtualization Benefit Licensing Guide.
For information about licensing your non-production or test SQL Server instances through Azure Arc, see Manage SQL Server licensed for non-production use.
License SQL Server instances by virtual cores
Licensing SQL Server by v-cores allows you to limit the scope of the license to a specific virtual machine (VM) and one or more SQL Server instances installed on the operating system environment (OSE) of that machine. It's optimized for the following scenarios:
- Your SQL Server VMs are mixed with the VMs running other software on the same physical servers.
- You deploy your VMs to a hosting partner or a third party cloud where you don't control your physical infrastructure.
You can choose v-core licensing to license both SQL Server software and SQL Server Extended Security Updates. V-core license is managed independently for each VM using SQL Server configuration panel. For your convenience, Overview of each Arc-enabled SQL Server resource shows the configured license under Host License Type.
Standard Edition is limited to a maximum of 24 v-cores even if the OSE is configured with more v-cores. Details in Compute capacity limits by edition of SQL Server.
For more information about licensing SQL Server by virtual cores, see section Licensing individual virtual machines in the SQL Server Licensing Guide.
License types
The following license types are supported when licensing v-cores:
License type | Description | Value |
---|---|---|
Pay-as-you-go | Subscribe to the Standard or Enterprise Edition service and be billed on an hourly meter. See SQL Server prices and licensing. | PAYG |
License with Software Assurance | Bring your own Standard or Enterprise Edition license with Software Assurance or SQL Subscription. Your software usage is reported using a free hourly meter according to the metering rules. See Metering software usage. | Paid |
License only | You use a perpetual or Server+CAL license for Standard or Enterprise Edition, or you use Developer, Evaluation, or Express Edition. Your software usage is reported according to the metering rules. See Metering software usage. | LicenseOnly |
Important
The pay-as-you-go subscription requires the hosting machine to be continuously connected to Azure.
Intermittent connectivity disruptions for up to 30 days are tolerated with built-in resilience. After 30 days without a connection, the pay-as-you-go subscription will expire. Once your subscription expires, you aren't authorized to use the software.
The pay-as-you-go hourly charges are issued only when SQL Server is running on the machine at any point within a given hour and if the machine is online.
By selecting License with Software Assurance, you attest that you have Enterprise Edition or Standard Edition licenses with active Software Assurance or a SQL subscription license.
In addition to billing differences, license type determines what features are available to your SQL Server instance.
The following table identifies features enabled depending on license type:
Feature | License only 1 | License with Software Assurance or SQL subscription |
Pay-as-you-go |
---|---|---|---|
Connect to Azure Arc | Yes | Yes | Yes |
SQL Server inventory | Yes | Yes | Yes |
Best practices assessment | No | Yes | Yes |
Migration readiness (preview) | Yes | Yes | Yes |
Detailed database inventory | Yes | Yes | Yes |
Microsoft Entra authentication | Yes | Yes | Yes |
Microsoft Defender for Cloud | Yes | Yes | Yes |
Govern through Microsoft Purview | Yes | Yes | Yes |
Automated backups to local storage (preview) | No | Yes | Yes |
Point-in-time restore | No | Yes | Yes |
Automatic updates | No | Yes | Yes |
Failover cluster instances | Yes | Yes | Yes |
Always On availability groups | Yes | Yes | Yes |
Monitoring (preview) | No | Yes | Yes |
Operate with least privilege | Yes | Yes | Yes |
1 License only includes SQL Server instances that are Developer, Express, Web, or Evaluation Edition and instances using a Server/CAL license.
Note
- License type is a required parameter when you install Azure Extension for SQL Server and each supported onboarding method includes the license type options.
- SQL Server 2022 (16.x) allows you to select the license type during setup. See Install Azure Extension for SQL Server from the Installation Wizard.
License SQL Server instances by physical cores without using VMs
This licensing option is optimized for the following scenarios:
- You control your physical environment and install the SQL Server instances on a physical server to maximize the performance of your databases application.
- Your SQL Server instance uses a license without Software Assurance.
In this scenario, the licensing requirements are identical to Licensing SQL Server by virtual cores but the SQL Server software usage is reported based on the physical cores available to the OSE of that server. For details, see Metering software usage.
Standard Edition is limited to a maximum of 24 p-cores even if the OSE is installed on a larger machine. Details in Compute capacity limits by edition of SQL Server.
Important
If a physical machine without VMs is connected to Azure Arc in the scope that is covered by a SQL Server physical core license, the unlimited virtualization benefit will not apply to that machine. It will be licensed and billed separately.
For more information about licensing SQL Server on physical OSE, see section Core-based licensing in the SQL Server Licensing Guide.
License SQL Server instances by physical cores with unlimited virtualization
This licensing option is most effective when:
- You control your physical environment and install the SQL Server instances on different VMs for security isolation and better resource management.
- Your infrastructure and the selected payment method support the unlimited virtualization benefit (UV).
- Licensing your SQL Server instances by v-cores is more expensive than licensing the p-cores of the host.
To leverage the UV benefit, you need to create a SQLServerLicense resource covering the specific SQL Server - Azure Arc instances that you intend to include. For details of creating SQLServerLicense resources, see Create SQL Server license.
Caution
The UV benefit is not available to VMs running on any listed providers' infrastructure. They can only be licensed by v-cores. If you create a SQLServerLicense resource with the intent of licensing these VMs using UV, you will be charged for the consumption of v-cores based on the SQL Server configuration of the host, and any existing p-core licenses will not apply to offset such charge. See Listed providers for details.
A single SqlServerLicense resource can cover multiple virtual machines connected to Azure Arc. It includes several properties that define how the license is applied and billed.
The License category is set to Core
to represent SQL Server physical core license.
The Scope property sets the Azure scope in which all qualified Machine - Azure Arc resource are covered by the license. The following Azure scopes are supported:
- Azure tenant
- Azure subscription
- Resource group
To qualify, each Machine - Azure Arc resource must be configured to use a physical core license. Otherwise, the Machine - Azure Arc resource must be licensed for SQL Server individually. See Licensing SQL Server by virtual cores.
The Size property of the license resource represents the sum of physical cores of the servers to which the license will be applied. The minimum size of the license is 16 p-cores.
The Subscription property defines which Azure subscription will be used for billing and invoicing when the license is active.
The license resource can be created in a resource group in any of the supported regions. For the list of supported regions, see Supported Azure regions. The location of the resource is set to the location of the selected resource group. The location of the license resource doesn't impact the scope. It will apply to ALL Machine - Azure Arc resources in the scope of the license regardless of the regions where these resources are onboarded.
Important
Multiple license resources can be associated with the same scope or overlapping scopes. For example, a new license can be added when additional physical servers are deployed during temporary bursts of activity, or to reflect unexpected growth. All the virtual machines running on these physical servers must be connected to Azure Arc in the scope of the license resource.
The Billing plan property provides a choice between paying for the license on an hourly meter or by bringing your own license.
Billing plan | Description | Value |
---|---|---|
Pay-as-you-go | By selecting this option you subscribe to unlimited virtualization service that is billed on an Enterprise Edition hourly meter. See SQL Server prices and licensing. | PAYG |
Bring-your-own-license | By selecting this option you attest that you have an active Enterprise Edition license with Software assurance or a SQL subscription for the same or greater number of cores, and wish to use that license to cover the usage of the SQL Server software on each VM in its scope leveraging the unlimited virtualization benefit. | Paid |
Important
To ensure the correct application of the p-core license, make sure that each VM in the scope you wish to be licensed:
- has the Physical core license property set to True.
- has the License type property set to match the selected Billing plan of the p-core license.
For more details, see Apply physical core license.
The Activation state property controls when the license takes effect. The license can be activated during creation, or created first and then activated at a later time. The delayed activation allows you to coordinate it with other events in the licensing lifecycle, such as the expiration of an existing Enterprise Agreement. The Last activated and Last deactivated timestamp properties show when the license was last activated and deactivated. For more details, see Change SQL Server license properties.
The Tenant ID property is automatically set when the tenant scope is selected.
For more information about licensing by physical cores with unlimited virtualization, see section Licensing for maximum virtualization in the SQL Server Licensing Guide.
Manage SQL Server licensed for non-production use
If you have your production environment managed through Azure Arc using one of the supported licensing options, you can use SQL Server for non-production purposes for free. There are two ways you can take advantage of this benefit when using SQL Server enabled by Azure Arc.
Use SQL Server Developer Edition
SQL Server Developer Edition is free and can be used in any Azure subscription. The Azure extension for SQL Server will detect it and report the usage via a $0 Dev edition meter even if the License type of the host is set to Paid
or PAYG
. The Developer Edition has the same feature set as Enterprise Edition. For more details, see Metering software usage.
Use Azure dev/test subscription
If you configure the non-production environment as a mirror of the production environment, and want to use the same editions as in production, you must connect the hosting machines and SQL Server instances to an Azure dev/test subscription. The SQL Server meters in a dev/test subscription will be nullified. For information on how to create a dev/test subscription on Azure, see Creating Enterprise and Organization Azure Dev/Test Subscriptions.
For more information, see section Licensing SQL Server for non-production use in the SQL Server Licensing Guide.
Manage SQL Server licensed for high availability and disaster recovery
If your SQL Server instance is a passive replica created as part of your high availability or disaster recovery configuration, you are entitled to the failover benefits that are included if your license type is set to Paid
or PAYG
. For more information about the failover benefits, see section Licensing SQL Server for high availability and disaster recovery in the SQL Server Licensing Guide.
To help you manage the failover benefits and remain compliant, Azure extension for SQL Server automatically detects the passive instances and reflects the use of the SQL Server software by emitting special $0 disaster recovery (DR) meters, as long as you properly configured the license type property. For more details, see Metering software usage.
Manage SQL Server instances with a Server+CAL license
You can connect any licensed SQL Server instance to Azure Arc, including the ones that are licensed with the Server+CAL licensing model. If your instance uses this license you must set the license type to LicenseOnly
even if you have active Software assurance for it.
Note
If you have converted your Enterprise Server+CAL license to a core-based license, you should set the license type to Paid
or PAYG
. The best practice is to also to upgrade the SQL Server edition from Enterprise
to EnterpriseCore
as the latter provides the complete set of SQL Server capabilities. But even if you did not upgrade the instances, Azure extension for SQL Server will monitor software usage as EnterpriseCore
. For more details, see Metering software usage.
Metering software usage
The usage of the SQL Server software is reported once an hour. The specific meter is automatically selected based on the SQL Server edition and the number v-cores or p-cores visible to the Operating System Environment (OSE). The following rules apply:
If you install one or several SQL Server instances on a virtual machine and don't specify that a physical core license should be used, SQL Server software usage is metered based on the total number of virtual cores available to OSE, with a minimum of four cores per OSE.
If you install one or several SQL Server instances on a physical server without using virtual machines, SQL Server software usage is metered based on the total number physical cores available to the OSE, with a minimum of four cores per OSE.
SQL Server software usage is reported per OSE whether one or multiple SQL Server instances are installed on the same OSE.
If two or more instances of the same edition are installed, the first instance in alphabetical order will report usage.
The combination of the selected License Type and the highest SQL Server edition installed on the OSE defines which meter will be sent every hour.
For more information, see SQL Server Licensing Resources and Documents.
The next table shows the meter SKUs that are used for metering and billing for SQL Server software installed on a single OSE:
Installed edition | Projected edition | License type | Failover replica | Use p-core license | Meter SKU |
---|---|---|---|---|---|
Enterprise Core | Enterprise | PAYG |
No | No | Ent edition - PAYG |
Enterprise Core | Enterprise | PAYG |
No | Yes | Ent edition - Virtual license 2 |
Enterprise Core | Enterprise | Paid |
No | No | Ent edition - AHB |
Enterprise Core | Enterprise | Paid |
No | Yes | Ent edition - Virtual license 2 |
Enterprise Core | Enterprise | LicenseOnly |
Yes or No | n/a | Ent edition - License only |
Enterprise Core | Enterprise | PAYG or Paid |
Yes | Yes or No | Ent edition - DR replica |
Enterprise 1 | Enterprise | PAYG |
No | No | Ent edition - PAYG |
Enterprise 1 | Enterprise | PAYG |
No | Yes | Ent edition - Virtual license 2 |
Enterprise 1 | Enterprise | Paid |
No | No | Ent edition - AHB |
Enterprise 1 | Enterprise | Paid |
No | Yes | Ent edition - Virtual license 2 |
Enterprise 1 | Enterprise | LicenseOnly |
Yes or No | n/a | Ent edition - License only |
Enterprise 1 | Enterprise | PAYG or Paid |
Yes | Yes or No | Ent edition - DR replica |
Standard | Standard | PAYG |
No | No | Std edition - PAYG |
Standard | Standard | PAYG |
No | Yes | Std edition - Virtual license 2 |
Standard | Standard | Paid |
No | No | Std edition - AHB |
Standard | Standard | Paid |
No | Yes | Std edition - Virtual license 2 |
Standard | Standard | LicenseOnly |
No | n/a | Std edition - Virtual license 2 |
Standard | Standard | PAYG or Paid |
Yes | Yes or No | Std edition - DR replica |
Evaluation | Evaluation | Any | Yes or No | n/a | Eval edition |
Developer | Developer | Any | Yes or No | n/a | Dev edition |
Web | Web | Any | n/a | n/a | Web edition |
Express | Express | Any | n/a | n/a | Express edition |
1 When Enterprise Edition is installed, it indicates that the Server/CAL licensing model is used. See Manage SQL Server instances with a Server+CAL license for more information.
2 This meter reflects the software usage covered by the p-core license and the unlimited virtualization benefit. The SQL Server instance must be installed on a virtual machine to be covered.
The next table shows the meter SKUs that are used for metering and billing for SQL Server software covered by a physical core license with unlimited virtualization:
License category | Projected edition | Billing plan | Meter SKU |
---|---|---|---|
P-core license | Enterprise | PAYG |
Ent edition - Host - PAYG |
P-core license | Enterprise | Paid |
Ent edition - AHB |
Related content
الملاحظات
https://aka.ms/ContentUserFeedback.
قريبًا: خلال عام 2024، سنتخلص تدريجيًا من GitHub Issues بوصفها آلية إرسال ملاحظات للمحتوى ونستبدلها بنظام ملاحظات جديد. لمزيد من المعلومات، راجعإرسال الملاحظات وعرضها المتعلقة بـ