Lost connection to Azure Managed instances

Abhishek Jain 25 Reputation points
2023-09-23T13:53:46.8233333+00:00

During Wednesday 20th Sep, Azure Maintenance on our Production subscription, made our application lost connection on managed SQL instances. It was mentioned that during maintenance there could be small connectivity blips but we were down for almost 4 hours until, we were advised by support line to scale up our instance that would trigger restart. This workaround did helped but its unfortunate to happen to Production environment and the only resolution is restart. It could have been easier if Microsoft had enabled Start/Stop button for all subscriptions, instead of scale up/down that made the instance spin for ~90 mins. Did anyone else noticed this scenario, is their any other workaround with less turnaround time.

Azure SQL Database
Azure Managed Applications
Azure Managed Applications
An Azure service that enables managed service providers, independent software vendors, and enterprise IT teams to deliver turnkey solutions through the Azure Marketplace or service catalog.
139 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. ShaktiSingh-MSFT 15,301 Reputation points
    2023-09-26T04:53:36.5133333+00:00

    Hi
    Abhishek Jain    ,

    Welcome to Microsoft Q&A forum and thanks for using Azure Services.

    We are sorry about the inconvenience you are facing.

    As I understand, your Azure SQL Managed Instance was down for about 4 hours during maintenance activity.

    We have Start Stop feature in preview for Azure SQL MI as illustrated here: https://video2.skills-academy.com/en-us/azure/azure-sql/managed-instance/instance-stop-start-how-to?view=azuresql&tabs=azure-portal.

    It has one of the limitation that you can't stop instances that:

    You could try to implement Retry Logic:

    It is strongly recommended that your client program has retry logic so that it could reestablish a connection after giving the transient fault time to correct itself. We recommend that you delay for 5 seconds before your first retry. Retrying after a delay shorter than 5-seconds risks overwhelming the cloud service. For each subsequent retry the delay should grow exponentially, up to a maximum of 60 seconds.

    For code examples of retry logic, see:

    Also, if above does not help, we recommend you to raise support case so that the matter could be investigated deeply.

    Let us know if you need any further assistance.

    Thank you.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.