This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(172.8, 5%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I am running a serverless database.
It does not switch from the suspended state to the active state, it cannot connect from the local environment and times out.
If the data source called from Excel is specified in the database, it will fail with a timeout.
The database itself is active because the results are returned when the query is executed directly in "AzurePortal".
If you know the cause and solution of the above connection failure, please reply.
I also made a connection in SSMS and confirmed that the connection failed.
In addition, the firewall settings are set to allow communication to port 1433.
In case unconnnected, changing the AzureDB core CPU settings and I'll be able to connect after reconfiguring the database.
Therefore, I supporse that it is not due to improper firewall settings.
Based on the above, do you have any idea what causes the connection to fail?
An Azure relational database service.
Hi, @片口 翔太 Welcome to the Microsoft Q&A forum, Thanks for posting your question.
Since you have the correct firewall with 1433 and connection to SSMS I feel this needs to be investigated more by raising a support case.
Please let me know if you need any help in raising a support case.
Regards
Geetha
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 66%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EW%3C/text%3E%3C/svg%3E)
This is by design for now. The serverless database needs to transition and restart, and at that time, your connection is broken and needs to be retried. For all my serverless databases, the first connection always fails. This means with SSMS, Excel and clients you do not code, you will get a failure and need to retry manually. For software you code, I would add an automatic retry.