We're using Azure SQL Serverless tier. Quite often the database has stopped, and it's natural that it take a while to warm up and connect. However, it does not appear that there is a mechanism within the client libraries that will honour the connection timeout value in this instance. The connection seems to fail on cold start every time the first time around, with a subsequent connection being successful. Obviously we can (and should anyway) write resilient retry logic, but it would be good if the client libraries would at least allow for a connection to succeed given a long enough timeout period. Are there any upcoming revisions to the ADO.NET (or other) client libraries to help with this?
