Cannot connect to Azure Synapse serverless db - Currently Unabailable

WZIAFP 247

One of our business critical database is reporting the following error when connecting for over 2 hours:

TITLE: Error

Database 'xxxxxxx' on server 'xxxxxxxxxxxxx-ondemand.sql.azuresynapse.net' is not currently available. Please retry the connection later. If the problem persists, contact customer support, and provide them the session

For help, click: https://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=40613&LinkId=20476

Pilladi Padma Sai Manisha 11,715 Reputation points Microsoft External Staff Moderator

2026-04-14T10:59:05.0533333+00:00

Hi WZIAFP,
Thankyou for reaching microsoft Q&A!
The error you’re seeing (40613 – “Database is not currently available”) is not related to your query, authentication, or network configuration.

In Azure Synapse serverless SQL pools, this error typically indicates that the on-demand SQL endpoint is temporarily unavailable on the service side. Since serverless pools rely on dynamic compute allocation, the underlying infrastructure is fully managed by Microsoft, and backend availability or capacity issues can sometimes surface as this error.

Given that the issue has persisted for multiple hours, the endpoint involved is ondemand.sql.azuresynapse.net, and the failure is consistently reproducible, this strongly points to a platform-side disruption rather than anything within your environment.

You can retry the connection periodically, as these issues are often transient. It’s also worth checking Azure Service Health to see if there are any reported incidents affecting Synapse in your region. If the issue continues, it would be best to raise a Microsoft support ticket and include the session ID {E5028EA1-97B1-4CAE-AAAC-7B807975DEC0}, along with the connection ID and timestamp, so the backend team can investigate further.

this is a backend availability issue in Azure Synapse serverless SQL pool, and resolution depends on service recovery rather than changes on your side.
Pilladi Padma Sai Manisha 11,715 Reputation points Microsoft External Staff Moderator

2026-04-20T11:12:29.2633333+00:00

Hi WZIAFP,
I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.

1 answer

AI answer

2026-04-14T09:37:56.37+00:00
Error 40613 indicates that the database on the Synapse serverless endpoint is currently unavailable and that the issue is expected to be transient.

For a serverless SQL pool in Azure Synapse, take these steps:

Treat it as a transient connectivity issue

Error 40613 is documented as a transient fault: the database is not currently available and the client should retry the connection.

Implement retry logic in the client (with backoff) instead of failing immediately. If the duration of failures exceeds about a minute or you see repeated occurrences during the day, it is considered abnormal and should be escalated.

Check service and workspace health

Check the Azure status page for any regional issues affecting Azure SQL or Synapse.

In the Azure portal, open the Synapse workspace and check Resource Health and Activity Log for the serverless SQL pool to see if there are ongoing platform incidents or maintenance.

Verify that the issue is not just warm-up

Serverless SQL pool deactivates after inactivity and needs to warm up on the first connection. Normally, a simple retry with proper ConnectionRetryCount and ConnectRetryInterval and a sufficient overall Connection Timeout resolves this.

Ensure the connection timeout is greater than ConnectRetryCount * ConnectRetryInterval so that all retries can complete.

If the error has persisted for more than a few minutes (as in this case, over 2 hours), it is no longer just a warm-up delay and should be treated as a platform issue.

Confirm connectivity from the client side

From the client machine, verify that the workspace serverless endpoint xxxxxxxxxxxxx-ondemand.sql.azuresynapse.net resolves and is reachable (DNS and network).

Ensure that outbound access to *.database.windows.net / Synapse endpoints and port 1443 is not blocked by local or corporate firewalls or network security devices.

If using a tool that is not Synapse-aware, connect using the same options used for SQL Server/Azure SQL Database, specifying the -ondemand server name and a valid database name (for example, master).

If the problem persists beyond transient expectations

Because this is a business-critical database and the error has already persisted for hours, open an Azure support ticket from the Azure portal.

Include:

The exact error message and code (40613).

The session tracing ID from the error ({E5028EA1-97B1-4CAE-AAAC-7B807975DEC0}).

The connection ID and timestamps.

Region and workspace name.

Azure support can correlate the session tracing ID with backend logs to identify whether there is a platform-side issue with the serverless SQL pool or the specific database.

If any client applications are not yet using retry logic, update them to handle transient faults (40197, 40613, and similar) by retrying with exponential backoff, as recommended for cloud databases.

References:

Troubleshoot connectivity issues and other errors

Database Engine events and errors (31000 to 41399)

Troubleshoot serverless SQL pool in Azure Synapse Analytics

Synapse Studio troubleshooting
AI-generated content may be incorrect. Read our transparency notes for more information.
Was this answer helpful?

1 person found this answer helpful.

Your answer