Azure SQL Serverless cold start connection errors

%3CLINGO-SUB%20id%3D%22lingo-sub-1833387%22%20slang%3D%22en-US%22%3EAzure%20SQL%20Serverless%20cold%20start%20connection%20errors%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1833387%22%20slang%3D%22en-US%22%3E%3CP%3EWe're%20using%20Azure%20SQL%20Serverless%20tier.%20Quite%20often%20the%20database%20has%20stopped%2C%20and%20it's%20natural%20that%20it%20take%20a%20while%20to%20warm%20up%20and%20connect.%20However%2C%20it%20does%20not%20appear%20that%20there%20is%20a%20mechanism%20within%20the%20client%20libraries%20that%20will%20honour%20the%20connection%20timeout%20value%20in%20this%20instance.%20The%20connection%20seems%20to%20fail%20on%20cold%20start%20every%20time%20the%20first%20time%20around%2C%20with%20a%20subsequent%20connection%20being%20successful.%20Obviously%20we%20can%20(and%20should%20anyway)%20write%20resilient%20retry%20logic%2C%20but%20it%20would%20be%20good%20if%20the%20client%20libraries%20would%20at%20least%20allow%20for%20a%20connection%20to%20succeed%20given%20a%20long%20enough%20timeout%20period.%20Are%20there%20any%20upcoming%20revisions%20to%20the%20ADO.NET%20(or%20other)%20client%20libraries%20to%20help%20with%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

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?

0 Replies