Pricing guidance for SQL Server on Azure VMs

Applies to: SQL Server on Azure VM

This article provides pricing guidance for SQL Server on Azure Virtual Machines. There are several options that affect cost, and it is important to pick the right image that balances costs with business requirements.

Free-licensed SQL Server editions

If you want to develop, test, or build a proof of concept, then use the freely licensed SQL Server Developer edition. This edition has all the features of SQL Server Enterprise edition, allowing you to build and test any type of application. However, you cannot run the Developer edition in production. A SQL Server Developer edition VM only incurs charges for the cost of the VM, because there are no associated SQL Server licensing costs.

If you want to run a lightweight workload in production (<4 cores, <1-GB memory, <10 GB/database), use the freely licensed SQL Server Express edition. A SQL Server Express edition VM also only incurs charges for the cost of the VM.

For these development/test and lightweight production workloads, you can also save money by choosing a smaller VM size that matches these workloads. The D2as_v5 might be a good choice in some scenarios.

To create an Azure VM running SQL Server 2022 with one of these images, see the following links:

Paid SQL Server editions

If you have a non-lightweight production workload, use one of the following SQL Server editions:

You have two options to pay for SQL Server licensing for these editions: pay per usage or Azure Hybrid Benefit.

Pay per usage

Paying the SQL Server license per usage (also known as pay as you go) means that the per-second cost of running the Azure VM includes the cost of the SQL Server license. You can see the pricing for the different SQL Server editions (Web, Standard, Enterprise) in the Azure Virtual Machines pricing page for Windows or Linux.

The cost is the same for all versions of SQL Server (2012 SP3 to 2022). The per-second licensing cost depends on the number of VM vCPUs.

Paying the SQL Server licensing per usage is recommended for:

• Temporary or periodic workloads. For example, an app that needs to support an event for a couple of months every year, or business analysis on Mondays.

• Workloads with unknown lifetime or scale. For example, an app that may not be required in a few months, or which may require more, or less compute power, depending on demand.

To create an Azure VM running SQL Server 2022 with one of these pay-as-you-go images, see the following links:

Azure Hybrid Benefit (AHB)

Azure Hybrid Benefit, also referred to as AHB, is a program that allows customers to use existing SQL Server core licenses with Software Assurance in an Azure VM. A SQL Server VM using AHB only charges for the cost of running the VM, not for SQL Server licensing, given that you have already acquired licenses and Software Assurance through a Volume Licensing program or through a Cloud Solution Partner (CSP).

Bringing your own SQL Server licensing through Azure Hybrid Benefit is recommended for:

• Continuous workloads. For example, an app that needs to support business operations 24x7.

• Workloads with known lifetime and scale. For example, an app that is required for the whole year and which demand has been forecasted.

To use AHB with a SQL Server VM, you must have a license for SQL Server Standard or Enterprise and Software Assurance, which is a required option through some volume licensing programs and an optional purchase with others. The pricing level provided through Volume Licensing programs varies, based on the type of agreement and the quantity and or commitment to SQL Server. But as a rule of thumb, Azure Hybrid Benefit for continuous production workloads has the following benefits:

Reduce costs

To avoid unnecessary costs, choose an optimal virtual machine size and consider intermittent shutdowns for non-continuous workloads.

Correctly size your VM

The licensing cost of SQL Server is directly related to the number of vCPUs. Choose a VM size that matches your expected needs for CPU, memory, storage, and I/O bandwidth. For a complete list of machine size options, see Windows VM sizes and Linux VM sizes.

For more information on choosing the best VM size for your workload, see VM size best practices.

Shut down your VM when possible

If you are using any workloads that do not run continuously, consider shutting down the virtual machine during the inactive periods. You only pay for what you use.

For example, if you are simply trying out SQL Server on an Azure VM, you would not want to incur charges by accidentally leaving it running for weeks. One solution is to use the automatic shutdown feature for the underlying virtual machine:

Automatic shutdown is part of a larger set of similar features provided by Azure DevTest Labs.

For other workflows, consider automatically shutting down and restarting Azure VMs with a scripting solution, such as Azure Automation.

Next steps

For general Azure pricing guidance, see Prevent unexpected costs with Azure billing and cost management. For the latest Azure Virtual Machines pricing, including SQL Server, see the Azure Virtual Machines pricing page for Windows VMs and Linux VMs.

For an overview of SQL Server on Azure Virtual Machines, see the following articles:

• Overview of SQL Server on Windows VMs
• Overview of SQL Server on Linux VMs