Azure SQL Data Warehouse: How to setup Reserved Capacity

by May 5, 2019

Purchase your Azure SQL Datawarehouse Reservation


Since a few weeks you can buy Reserved Capacity for an Azure SQL Datawarehouse (SQLDW). This Reservation can save you up to 65% on the normal Pay as You go rates with a 3 year pre-commit. A pre-commit of 1 year will be discounted up to 35%.

These savings will only effect the compute power. You will charged separately for the storage with the normal Pay as You go rates.

To purchase a reservation,  you need to sign-in to the Azure Portal first and then search for reservations.

Reserved Capacity Azure SQLDW

After you have clicked on Purchase Now, you will need to choose the Azure SQLDW option.

Reserved Capacity Azure SQLDW

Select the Region, be aware that if you want to run Several SQLDW’s (Dev/Test/Prod) and you want to make use of the benefits of the reserved capacity that these SQLDW’s must all be created in the Region in which the reservation is made.

When you’re running a Enterprise Subscription and you have more then 1 Subscription you can change the Scope to  “Shared”. With this option selected you can use the Reserved Capacity across all subscription within the same EA Enrollment.

Reserved Capacity Azure SQLDW

Select 1 or 3 year Term.

Reserved Capacity Azure SQLDW

Choose a quantity. The reserved capacity is calculated by 100 cDWU(Data Warehouse units). Choose the quantity you want to reserved. In case you select 5 cDWU, you will have 500 cDWU of reserved capacity every hour.

Reserved Capacity Azure SQLDW


Reserved Capacity Azure SQLDW

The last step is to Purchase your Reservation.

Reserved Capacity nice to know’s

Storage and Network are charged separately, for these Azure Services the Reserved Capacity Discount will not be applied.

The Reserved Capacity Discount is applied on running Azure SQLDW Instances on a hourly basis.

If you don’t have a Azure SQLDW Instance deployed for an hour, then the reserved capacity is wasted for that hour. It doesn’t carry over. Unless you have more then 1 Azure SQLDW Instance running, the reservation is automatically applied to other matching instances in that hour.

Some Examples:

1 – Running 1 Azure SQLDW Instance:

You have purchased 5 units of 100 cDWU.

On the moment you scale to 1000 cDWU, you will be charged with a Pay as You go rates for 700 cDWU.

2 – Running 2 Azure SQLDW Instances:

You have purchased 15 units of 100 cDWU.

1 Azure SQLDW Instance is running 500 cDWU and the other one 1000 cDWU.

No extra cost will be applied.

3 – Running 2 Azure SQLDW Instances:

You have purchased 15 units of 100 cDWU.

1 Azure SQLDW Instance is running 500 cDWU from 9 am to 5 pm  and the other one 1500 cDWU the whole day.

You will be charged for a Pay as You go rates for 500 cDWU from 9 am to 5 pm.

Reserved Capacity Azure SQLDW

Thank you for reading this article and hopefully it will make things clear to you.

Within a few days I will publish a new article in which I describe how much you could possibly save if you still want to scale up or down during certain periods of the day. If there are any questions left about this article, don’t hesitate to ask them to me.

UPDATE 6th May

Reserved Capacity versus Pas as You go

Azure SQL Data Warehouse: How to setup Reserved Capacity

Feel free to leave a comment


Submit a Comment

Your email address will not be published. Required fields are marked *

one × one =

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Scale your SQL Pool dynamically in Azure Synapse

Scale your Dedicated SQL Pool in Azure Synapse Analytics In my previous article, I explained how you can Pause and Resume your Dedicated SQL Pool with a Pipeline in Azure Synapse Analytics. In this article I will explain how to scale up and down a SQL Pool via a...

Updated Microsoft Purview Pricing and Applications

Microsoft Purview Pricing and introduction of Purview Applications The Microsoft Purview pricing page has been updated. Below I have listed most of the changes. The most important changes are the introduction of the Microsoft Purview Applications and the pricing of...

Blog Serie: Provision users and groups from AAD to Azure Databricks

Blog Series This blog post series contains topics on how to Provision users and groups from Azure Active Directory to Azure Databricks using the Enterprise Application(SCIM). This is a summary of the all the blogs I posted the last couple of days. I am very happy with...

Azure SQL Data Warehouse: Reserved Capacity versus Pay as You go

How do I use my Reserved Capacity correctly? Update 11-11-2020: This also applies to Azure Synapse SQL Pools. In my previous article you were introduced, how to create a Reserved Capacity for an Azure SQL Datawarehouse (SQLDW). Now it's time to take a look at how this...

Azure Data Factory: Generate Pipeline from the new Template Gallery

Last week I mentioned that we could save a Pipeline to GIT. But today I found out that you can also create a Pipeline from a predefined Solution Template.Template Gallery These template will make it easier to start with Azure Data Factory and it will reduce...

Provision users and groups from AAD to Azure Databricks (part 1)

Blog Serie: Provisioning identities from Azure Active Directory to Azure Databricks. Instead of adding users and groups manual to your Azure Databricks environment, you can also sync them automatically from your Azure Active Directory to your Azure Databricks account...

Azure Purview Pricing example

Azure Purview pricing? Note: Billing for Azure Purview will commence November 1, 2021. Updated October 31st, 2021 Pricing for Elastic Data Map and Scanning for Other Sources are changed and updated in the blog below. Since my last post on Azure Purview announcements...

Azure Synapse Analytics overwrite live mode

Stale publish branch In Azure Synapse Analytics and Azure Data Factory is an new option available "Overwrite Live Mode", which can be found in the Management Hub-Git Configuration. With this new option your can directly overwrite your Azure Synapse Analytics or Azure...

Using Azure Automation to generate data in your WideWorldImporters database

CASE: For my test environment I want to load every day new increments into the WideWorldImporters Azure SQL Database with Azure Automation. The following Stored Procedure is available to achieve this. EXECUTE DataLoadSimulation.PopulateDataToCurrentDate...

Azure Purview announcements and new functionalities

This week the Azure Purview Product team added some new functionalities, new connectors(these connectors where added during my holiday), Azure Synapse Data Lineage, a better Power BI integration and the introduction of Elastics Data Map. Slowly we are on our way to a...