Frequent service health issue for Azure SQL DB

Question

We are encountering frequent service health issues for Azure SQL DB in one of our test subscription. We are getting the below service health issue.

“We're sorry your SQL database is unavailable at this time. Currently, Azure shows the downtime for your SQL database resource at a two-minute granularity. The actual downtime is likely less than a minute – average is 2s. We're working to determine the source of the problem.”

Currently, this DB is getting accessed using private link. We are not able to figure out the reason for the same. Does anybody have an idea of what the problem could be?

Answer 1

Thank you @Zagato36 and @pituach for looking into the issue and suggesting option to find the root cause. We had created a support request and we have been told that its due to Azure service itself. The last update received on 8-June-2020 where its mentioned that Product engineering team has applied a fix for the issue. I will update here once we get the detailed RCA.

Answer 2

Good day Kundan.

sorry your SQL database is unavailable at this time. Currently, Azure shows the downtime for your SQL database resource at a two-minute granularity. The actual downtime is likely less than a minute

In order to understand the issue we need more information.

1) always compare your log to the history of known issues

https://status.azure.com/en-us/status/history/

2) Let's start with the service tier that you are using, since I have a feeling that you are using "Azure SQL Database serverless", which make this report perfectly understandable.

Azure SQL Database serverless pause the service and it can take up to a minute to resume the service. This means that if for example you have a website which is not so active then you might have X time without any activity and the Azure Engine pause the service. First user which come to the website after the database was paused, will "wake up" the system and will need about a minute ton get the respond from the server. This might lead to time out.

3) Please review the following document on handling errors: Working with SQL Database connection issues and transient errors.

In the meantime what can you do?

Recommended in most cases to implement a "retry logic" to handle the intermittent issues. You can use geo-replication for regional issues. If you are having an issue with specific service (database) then you should create an Azure Support Request, so the team will be able to examine your specific service.

Answer 3

My apologies, I was not very clear. We are not using serverless. Please refer to the DB config below.