| title | description | services | documentationcenter | author | manager | editor | ms.assetid | ms.service | ms.custom | ms.workload | ms.tgt_pltfrm | ms.devlang | ms.topic | ms.date | ms.author |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Troubleshoot common connection issues to Azure SQL Database |
Steps to identify and resolve common connection errors for Azure SQL Database. |
sql-database |
dalechen |
cshepard |
ac463d1c-aec8-443d-b66e-fa5eadcccfa8 |
sql-database |
troubleshoot |
data-management |
na |
na |
article |
01/20/2017 |
daleche |
When the connection to Azure SQL Database fails, you receive error messages. This article is a centralized topic that helps you troubleshoot Azure SQL Database connectivity issues. It introduces the common causes of connection issues, recommends a troubleshooting tool that helps you identity the problem, and provides troubleshooting steps to solve transient errors and persistent or non-transient errors. Finally, it lists all the relevant articles for Azure SQL Database connectivity issues.
If you encounter the connection issues, try the troubleshoot steps that are described in this article. [!INCLUDE support-disclaimer]
Connection problems may be caused by any of the following:
- Failure to apply best practices and design guidelines during the application design process. See SQL Database Development Overview to get started.
- Azure SQL Database reconfiguration
- Firewall settings
- Connection time-out
- Incorrect login information
- Maximum limit reached on some Azure SQL Database resources
Generally, connection issues to Azure SQL Database can be classified as follows:
- Transient errors (short-lived or intermittent)
- Persistent or non-transient errors (errors that regularly recur)
If you encounter a specific connection error, try this tool, which will help you quickly identity and resolve your problem.
If your application is experiencing transient errors, review the following topics for tips about how to troubleshoot and reduce the frequency of these errors:
- Troubleshooting Database <x> on Server <y> is unavailable (Error: 40613)
- Troubleshoot, diagnose, and prevent SQL connection errors and transient errors for SQL Database
If the application persistently fails to connect to Azure SQL Database, it usually indicates an issue with one of the following:
- Firewall configuration. The Azure SQL database or client-side firewall is blocking connections to Azure SQL Database.
- Network reconfiguration on the client side: for example, a new IP address or a proxy server.
- User error: for example, mistyped connection parameters, such as the server name in the connection string.
- Set up firewall rules to allow the client IP address. For temporary testing purposes, set up a firewall rule using 0.0.0.0 as the starting IP address range and using 255.255.255.255 as the ending IP address range. This will open the server to all IP addresses. If this resolves your connectivity issue, remove this rule and create a firewall rule for a appropriately limited IP address or address range.
- On all firewalls between the client and the Internet, make sure that port 1433 is open for outbound connections. Review Configure the Windows Firewall to Allow SQL Server Access and Hybrid Identity Required Ports and Protocols for additional pointers related to additional ports that you need to open for Azure Active Directory authentication.
- Verify your connection string and other connection settings. See the Connection String section in the connectivity issues topic.
- Check service health in the dashboard. If you think there’s a regional outage, see Recover from an outage for steps to recover to a new region.
The following table lists every connection problem topic that applies directly to the Azure SQL Database service.
| Title | Description | |
|---|---|---|
| 1 | Troubleshoot connection issues to Azure SQL Database | This is the landing page for troubleshooting connectivity issues in Azure SQL Database. It describes how to identify and resolve transient errors and persistent or non-transient errors in Azure SQL Database. |
| 2 | Troubleshoot, diagnose, and prevent SQL connection errors and transient errors for SQL Database | Learn how to troubleshoot, diagnose, and prevent a SQL connection error or transient error in Azure SQL Database. |
| 3 | General transient fault-handling guidance | Provides general guidance for transient fault handling when connecting to Azure SQL Database. |
| 4 | Troubleshoot connectivity issues with Microsoft Azure SQL Database | This tool helps identity your problem solve connection errors. |
| 5 | Troubleshoot "Database <x> on server <y> is not currently available. Please retry the connection later" error | Describes how to identify and resolve a 40613 error: "Database <x> on server <y> is not currently available. Please retry the connection later." |
| 6 | SQL error codes for SQL Database client applications: Database connection error and other issues | Provides info about SQL error codes for SQL Database client applications, such as common database connection errors, database copy issues, and general errors. |
| 7 | Azure SQL Database performance guidance for single databases | Provides guidance to help you determine which service tier is right for your application. Also provides recommendations for tuning your application to get the most out of your Azure SQL Database. |
| 8 | SQL Database Development Overview | Provides links to code samples for various technologies that you can use to connect to and interact with Azure SQL Database. |