This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Community Hub.
We are pleased to announce that the Hyperscale elastic pools preview now also supports configuring a specific maintenance schedule to use for a pool. This makes impactful maintenance events predictable and less disruptive for your workload. In addition, Advance notifications (Preview) are also available for Hyperscale elastic pools configured to use a non-default maintenance window.
Overview
By default, impactful updates to Azure SQL Database resources happen during the period 8AM to 5PM local time. With maintenance windows, you can adjust the window for maintenance updates to a time suitable for your workload, by choosing from two non-default maintenance window slots:
- Weekday window: 10:00 PM to 6:00 AM local time, Monday – Thursday
- Weekend window: 10:00 PM to 6:00 AM local time, Friday – Sunday
Once the maintenance window selection is made, all planned maintenance events will only occur during the window of your choice.
Regional availability
At this time, you can setup non-default maintenance windows for non-zone redundant Hyperscale elastic pools configured to use standard-series (“Gen5”) hardware, in the following regions:
- East US
- East US 2
- Central US
- West Europe
- US Gov Virginia
- US Gov Texas
Stay tuned, as we will soon release more regions and configurations (PRMS / MOPRMS; zone-redundant)!
Getting started
Detailed information is available at Configure maintenance window. For convenience, here’s a quick start to get you on your way!
Azure portal
Maintenance window can be set up for newly created as well as existing Azure SQL Database Hyperscale elastic pools using the Azure portal, CLI and PowerShell. More information on how to set up maintenance windows can be found here. Here’s a screenshot of an existing Hyperscale elastic pool in East US, with the available maintenance windows shown in the dropdown list:
Azure PowerShell
You can use the below script to get a list of supported maintenance configurations for a given region:
$configurations = Get-AzMaintenancePublicConfiguration
$configurations | ?{ $_.Location -contains "eastus" -and $_.MaintenanceScope -eq "SQLDB"}
You can then use the Id property returned from the above as the value for MaintenanceConfigurationId in commands like New-AzSqlElasticPool and Set-AzSqlElasticPool.
For example, the MaintenanceConfigurationId value of “/subscriptions/<<SUBSCRIPTION ID>>/providers/Microsoft.Maintenance/publicMaintenanceConfigurations/SQL_EastUS_DB_2” would be used for the Friday-Sunday 10PM-6AM maintenance window.
Azure CLI
Similarly, you can use az maintenance public-configuration (list / show) to get a list of maintenance configurations and then filter it by region. You can pass in the maintenance configuration ID as the parameter --maint-config-id in Azure Cli commands like az sql elastic-pool create and az sql elastic-pool update.
Advance notifications (preview)
You can also configure alerts for Hyperscale elastic pools to notify you about upcoming planned maintenance events - 24 hours in advance. More information on how to set up advance notification can be found here.
Conclusion
We look forward to you using maintenance windows to make impactful maintenance events predictable and less disruptive for your workloads using Hyperscale elastic pools. Our team is here to assist with any questions you may have. Please leave a comment on this blog and we’ll be happy to get back to you. Alternatively, you can also email us at sqlhsfeedback AT microsoft DOT com. We are eager to hear from you all!