Connectivity: Troubleshoot DB Availability and Connection Errors

Question

Connectivity: Troubleshoot DB Availability and Connection Errors

Venkata Ramana Reddy Beeram 0

Job failed due to reason: at Source 'NativeToWorkdayCompany': Cannot connect to SQL database: 'jdbc:sqlserver://azcfasqlp003.database.windows.net;database={CFA}', 'Service Principal ID: 583bea78-xxxxxxxxxxxx'.[SQL Exception]Error Code:40613, Error Message: Database 'CFA' on server '' is not currently available. Please retry the connection later. If the problem persists, contact customer support, and provide them the session tracing ID of '{8A7BA5D5-346F-49CE-82F3-xxxxxxxxx}'. ClientConnectionId:17aded4e-0bad-4937-90ad-xxxxxxxxxxxxxxxxx, error stack:shaded.msdataflow.com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:276) shaded.msdataflow.com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.java:329) shaded.msdataflow.com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:137) shaded.msdataflow.com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:42) shaded.msdataflow.com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(SQLSer

Erland Sommarskog 138K Reputation points MVP Volunteer Moderator

2026-10-13T14:09:58.2033333+00:00

Did this happen only once, or does it persist over a longer time? As the AI answer says, this can happen transiently for a number of reasons.

Generally, when you want help with something, it is always a good idea to give some context, rather than just dumping an error message. It is also a good idea to briefly describe what troubleshooting you have made on your own.

1 answer

Your answer

Erland Sommarskog 138K Reputation points MVP Volunteer Moderator

2026-10-13T14:09:58.2033333+00:00

Did this happen only once, or does it persist over a longer time? As the AI answer says, this can happen transiently for a number of reasons.

Generally, when you want help with something, it is always a good idea to give some context, rather than just dumping an error message. It is also a good idea to briefly describe what troubleshooting you have made on your own.

Answer 1

Error 40613 means the Azure SQL database is currently unavailable. The documented common causes are a transient failover or brief unavailability during a scale operation. In Azure SQL, this error can also appear if a Dedicated Admin Connection (DAC) session is already established for that database, and for serverless databases it can indicate the database is paused and needs time to resume.

Recommended troubleshooting path:

Retry the connection with backoff.
- This error is classified as transient.
- Use retry logic in the client or pipeline.
- A connection timeout of at least 30 seconds is recommended.
Verify basic connection settings.
- Confirm the JDBC connection string uses the fully qualified server name.
- Confirm the SQL port is 1433.
- Make sure TCP/IP is enabled on the client side.
Check whether the database is serverless and paused.
- If the database is serverless, 40613 can occur while the database is paused.
- Wait about one minute, then retry.
Check Azure Portal health information.
- Review Resource Health for the database/server to see whether there is an ongoing platform issue affecting availability.
If the issue persists for more than a few minutes:
- Capture the session tracing ID from the error.
- Contact support with that tracing ID.
If worker/resource pressure is suspected:
- Error 49918 indicates the service is busy due to insufficient resources.
- Error 10928 indicates a resource governance limit was reached.
- In sustained cases, reduce concurrency, shorten long-running operations, or scale up the database or elastic pool.

If the failure is happening only intermittently in the job, the most likely handling is resilient retry logic. If it continues consistently, check Resource Health and whether the database is serverless or under resource pressure, then escalate with the session tracing ID.

References: