Redaguoti

Bendrinti naudojant


Maintenance window FAQ for Azure SQL Managed Instance

This article answers frequently asked questions about the maintenance window for Azure SQL Managed Instance. For a maintenance window FAQ for Azure SQL Database, see Maintenance window FAQ.

Maintenance window availability and capability

What is the maintenance window feature?

The maintenance window feature provides you with the ability to limit Azure SQL managed instance maintenance outages to a prescheduled time block, outside your business hours. For more information, see Maintenance window schedules.

What is the default maintenance policy if I don't choose any specific window?

Maintenance events occur during the default window 5PM to 8AM local time, Monday - Sunday.

Users work in a different time zone than the Azure data center. Which time zone is local?

Local time is determined by the location of Azure region that hosts the resource and observes daylight saving time in accordance with local time zone definition. It isn't determined by the time zone configured on your managed instance.

In which regions are choosing a maintenance window available?

For Azure SQL Managed Instance choosing maintenance window is available in all Azure regions.

I don't see my region in the available regions list, what can I do?

Open a Support Ticket to share the feedback and check the plans for your region.

What is the pricing for maintenance window?

Configuring and using maintenance window is free of charge to all eligible Azure subscription types, see Maintenance window feature availability.

Would I receive a notification of the maintenance window?

You can opt in to receive notification up to 26 hours before the maintenance event, immediately before maintenance starts, and when the maintenance window is completed. The Resource health center can be checked for more information. To receive emails, advance notifications must be configured. For more information, see Advance notifications.

In which service level objectives (SLOs) can I choose a maintenance window?

Choosing a maintenance window is supported for all SLOs, but not supported on certain subscription types. For more information, see Maintenance window feature availability in Azure SQL Managed Instance.

How long does it take to process a maintenance window schedule change?

You can choose a different maintenance window at any time, but changing the maintenance window for an instance can be a long-running operation. For more information, see Azure SQL Managed instance management operations.

Does advance notification cover all maintenance events?

No, advance notifications focus only on planned maintenance events that can cause a service interruption.

Configuring a maintenance window

Can I choose a specific time/day for the maintenance window?

No, you can choose between prescheduled weekday or weekend windows. The maintenance can happen anytime or day within the window.

Can I cancel or postpone a planned maintenance event based on the received notification?

No. Cancelling or postponing an upcoming maintenance event isn't supported. Notifications help you to prepare for the event.

What are supported options to configure a maintenance window for an existing Azure SQL managed instance?

Azure portal, PowerShell, Azure CLI, and REST API.

I have the default maintenance window selected. Can I enable advance notifications for that maintenance?

Yes, this is currently available in Azure SQL Managed Instance.

Can I set alerts on the instance or resource group level?

No. Advance notifications are configured through Service Health alerts. Service health alerts support configuration of subscription, resource type, and region levels. Therefore, it is not possible to configure notification on the resource group level or instance level.

Can I configure alerts using PowerShell or Azure CLI?

There are no PowerShell and Azure CLI commands dedicated to configuring service health alerts. However, you can use an ARM template and leverage any standard method for deploying it by using CLI and PowerShell. Just follow the guidelines from the Quickstart: Create activity log alerts on service notifications using an ARM template.

Expectations during a maintenance window

What happens once I choose a maintenance window?

Configuring maintenance window is a long running asynchronous operation, similar to changing the service tier of your Azure SQL managed instance. The resource is available during the process, except a short reconfiguration that happens at the end of the operation and typically lasts up to 8 seconds, even during long-running transactions. To minimize the impact of the reconfiguration, you should perform the operation outside of the peak hours.

What types of updates are typically performed during a maintenance window?

The maintenance event can contain updates for all parts of the compute stack, including but not limited to hardware, firmware, operating system, the SQL database engine. They're typically combined into a single batch to minimize the incidence of maintenance events. For SQL Managed Instance, updates are combined in two batches, one focused on physical infrastructure, and another one focused on SQL engine and logical infrastructure. For Azure SQL Managed Instance, the IP address of the SQL managed instance changes.

How frequent are the updates?

For Azure SQL Managed Instance, customers can expect approximately two planned maintenance updates per month, but these updates can result with more than one maintenance event.

What can I expect during a maintenance event?

Maintenance event represents a period during which the updates are applied on the resource. Maintenance event happens inside the defined maintenance window. During a maintenance event, databases are fully available and accessible but some of the maintenance updates require a reconfiguration. For SQL Managed Instance, one update can result with multiple maintenance events. Depending on the configured maintenance window and start day of the update, the update events might complete within one week or overflow to the next week. However, planned maintenance events are never executed outside of defined maintenance windows.

How many reconfigurations can I expect during a maintenance event?

If the maintenance update requires a reconfiguration, typically between one and four reconfigurations happen during the window. Exceptionally, there can be more than four reconfigurations.

Prerequisites and preparation for a maintenance window

Can my application become resilient to reconfiguration events?

Yes, for application resilience during Gateway maintenance, make sure your client applications use the redirect connection policy. For resilience during reconfiguration, applications should follow retry logic concepts.

Are there any prerequisites for configuring maintenance window?

For Azure SQL Managed Instance, additional IP addresses are needed temporarily, as in scaling vCores scenario for corresponding service tier.

How do I validate that my SQL managed instances are set up for maintenance window?

Under settings of the Azure resource, the maintenance tab allows you to review and change the current maintenance plan schedule. You can also review and set the maintenance window schedules for multiple resources via PowerShell, CLI, or Azure API.

Can I check the list of resources that will be impacted by the event that I got notified for?

Yes, this information is available in Azure Monitor under the Service Health Planned Maintenance page, by visiting the single event. Another way is to retrieve the list of impacted resources by using Azure Resource Graph Explorer. You will receive an advance notification email that contains the notification ID and a link to the Azure Resource Graph Explorer.

Maintenance window monitoring

I'm not able to set up advance notifications for planned maintenance, will I still see planned maintenance event in Service Health dashboard?

For Azure SQL Managed Instance, planned maintenance events are visible in the Service Health dashboard, even if advance notifications aren't configured.

The notification says "In Progress", but window hasn't started yet?

There's a period of two hours in which notifications are sent. This means that you can receive notification up to 26 hours before the event, before the window opens, and after the window is closed. Even though the notification title is "In Progress", the content of the notification contains the maintenance window start and end time and that is the moment when maintenance will begin and end.

Is there a scenario where I don't get notification about planned event?

Yes, in case that you have created a new resource, executed scaling operation, or changed maintenance window, your SQL managed instance can end up on the machine that is already scheduled for upgrade. In this case, you are notified only when deployment window starts and ends. For all future deployments, you will get advance notification about planned events.

Can I check if my instance has been upgraded in the last X days?

What happens when a maintenance event fails?

Although rare, failures or interruptions during a maintenance event can occur. In the event of a failure, changes are rolled back and the maintenance will be rescheduled to another time.