SQL managed instance stuck on stage 2 of resizing for 12 hours

Hi Mark Windle

Greetings:

Typically, for resizing operations, you should expect the process to complete within a reasonable timeframe—most operations finish in under 60 minutes to 4 hours, depending on the type of resizing you are doing. Since it's already been 12 hours, here are a few steps you can take:

• Check the Azure Portal Activity Log: Look for any errors or warnings related to the resize operation. Sometimes the logs will show if the operation is pending, failed, or needs user intervention.
• Check for Blocking Operations: Sometimes, ongoing operations such as a restore can block the resizing process. You might want to verify if there are any active RESTORE operations running on your instance.
• Monitor the Azure Portal: Go to the Azure portal and check the notifications and status of your managed instance. This can give clues about whether the operation is still in progress or if there are any errors indicating why it's stuck.
• Verify storage limits: if your instance is close to the maximum storage limit (e.g. 8 TB for General Purpose), the operation might be delayed or blocked. You can query master.sys.server_resource_stats to check usage.
• Restart the Managed Instance: While not always recommended, some users have reported that restarting the instance can help nudge a stuck operation forward — but only do this during a maintenance window, as it will cause downtime.
• Retry the Operation: If there appears to be no ongoing blocking operations, you can consider cancelling the resizing operation and then attempting to resize it again.

If these steps do not resolve the issue, could you please share the requested details via private message as it will help us conduct a more thorough investigation.

I hope this information helps. Please do let us know if you have any further queries.

I can't say I know what to these logs mean exactly but these are the ones over the period. The only errors I've seen in the logs are when I hit the cancel button on the operator several hours later, and they failed.

The 5th item from the bottom maybe suggests a restore was happening, I'm not certain.

Querying server_resoute_stats gives me this, though I'm not sure if it's of any use. I'm guessing you didn't mean on the managed instance.

After all this though, it's cleared the issue as of about 5 minutes ago. I can't say why.