Azure SQL Database: Error 40613 on first connection to a paused serverless database

[field notes]: Set Connection Timeout=60 in the connection string (the 30-second default turns every cold start into a failure) and retry 40613/40501/10928/10929 with exponential backoff on a fresh connection, because the old handle is dead. Do not retry 18456 (wrong password) or 208 (missing table): those are permanent and retrying just slows a clear failure.

Context: The first connection of the day to an Azure SQL serverless database fails with Error 40613 (Database is not currently available) while the platform resumes it, which takes 30-60 seconds. A few seconds after resume it may briefly throttle (40501, 10928/10929). None of these are bugs.

Matched source

Source: Source: https://github.com/stepvda/railpulse_cloud Original query: "Azure SQL Database: Error 40613 on first connection to a paused serverless database" Key terms: 40613, azure, connection, database, error, first, paused, serverless

Source: The first connection of the day to an Azure SQL serverless database fails with Error 40613 (Database is not currently available) while the platform resumes it, which takes 30-60 seconds. A few seconds after resume it may briefly throttle (40501, 10928/10929). None of these are bugs.

Verified resolution: [field notes]: Set Connection Timeout=60 in the connection string (the 30-second default turns every cold start into a failure) and retry 40613/40501/10928/10929 with exponential backoff on a fresh connection, because the old handle is dead. Do not retry 18456 (wrong password) or 208 (missing table): those are permanent and retrying just slows a clear failure.

Source URL: https://github.com/stepvda/railpulse_cloud