The operation could not be completed because a service tier change is in progress for managed instance 'xxxxxxxx'.

Question

I have a SQL server managed Instance and trying to make a copy of exiting database on same managed instance using restore operation but getting error --

"The operation could not be completed because a service tier change is in progress for managed instance 'ManagedInstanceName' Please wait for the operation in progress to complete and try again"

Answer 1

It sounds like a service tier change is currently in progress on your Azure SQL MI (Managed instance). This can temporarily prevent other operations, such as restoring a database.

You can opt to wait for the operation to complete. You can check the status of the service tier change operation in the Azure portal. After confirming that the service tier change is complete, try the restore operation again.

If the service tier change seems stuck or takes an unusually long time, consider reaching out to Azure Support for further assistance.

Answer 2

Hi,

Check the status of the Managed Instance from the Overview blade. If it is in an "Updating" or "Not Available" state, verify if any scaling operations are in progress.

Additionally, check the Resource Health under the Help tab to assess the health of your SQL Managed Instance. You can also review the Activity Log, which tracks subscription-level events and operations for Azure resources.

Once the Managed Instance status changes to "Available," you can retry the copy operation.

Thank You!

Answer 3

Hi @Pramod Kumar Singh,

Thanks for the Question and using Microsoft Q&A

In addition to the response provided by @Alberto Morillo and RahulRandive, I would like to add the following information.

As we understand that, you are encountering an issue with your SQL Server Managed Instance where a service tier change is being reported as in progress, even though you haven't initiated one. This can sometimes happen due to a temporary glitch or an incomplete previous operation.

Here are a few steps you can try to resolve this issue:

• Even if the databases appear online and applications are connecting without issues, there may be a background operation that is still in progress. You can check the status of ongoing operations using the Azure portal or by querying the system views in SQL Server. You can run the following query to check for any ongoing operations and Look for any requests that might indicate a service tier change or other long-running operations.

SELECT * 
FROM sys.dm_exec_requests 
WHERE status = 'running' OR status = 'suspended';

• Sometimes, the Azure portal may provide notifications or alerts regarding ongoing operations. Check the notifications area in the Azure portal for any messages related to your managed instance.
• If you identify that a service tier change or another operation is indeed in progress, you may need to wait for it to complete. Depending on the size of the database and the nature of the operation, this could take some time.
• If you believe that there are no ongoing operations and the error persists, you might consider restarting the managed instance. This can sometimes clear up transient issues. However, be cautious with this approach, as it will temporarily disconnect all applications connected to the instance.
• Visit the Azure Service Health dashboard to check if there are any ongoing issues or outages affecting Azure SQL Managed Instances in your region. Sometimes, service disruptions can lead to unexpected behavior.

Please find the below mentioned link for more information.

https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/doc-changes-updates-known-issues?view=azuresql#change-service-tier-and-create-instance-operations-are-blocked-by-ongoing-database-restore

If the issue still persists, please let us know here. We will respond with more details and try to help you.

I hope, This response will address your query and helped you to overcome on your challenges.

If this answers your query, do click Accept Answer and Yes for was this answer helpful.