You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/data-factory/connector-troubleshoot-synapse-sql.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
-
title: Troubleshoot the Azure Synapse Analytics, Azure SQL Database, and SQL Server connectors
2
+
title: Troubleshoot the Azure Synapse Analytics, Azure SQL Database, SQL Server, Azure SQL Managed Instance, and Amazon RDS for SQL Server connectors
3
3
titleSuffix: Azure Data Factory & Azure Synapse
4
-
description: Learn how to troubleshoot issues with the Azure Synapse Analytics, Azure SQL Database, and SQL Server connectors in Azure Data Factory and Azure Synapse Analytics.
4
+
description: Learn how to troubleshoot issues with the Azure Synapse Analytics, Azure SQL Database, SQL Server connectors, Azure SQL Managed Instance, and Amazon RDS for SQL Server in Azure Data Factory and Azure Synapse Analytics.
5
5
author: jianleishen
6
6
ms.author: jianleishen
7
7
ms.reviewer: joanpo, wiassaf
@@ -14,11 +14,11 @@ ms.custom:
14
14
- synapse
15
15
---
16
16
17
-
# Troubleshoot the Azure Synapse Analytics, Azure SQL Database, and SQL Server connectors in Azure Data Factory and Azure Synapse
17
+
# Troubleshoot the Azure Synapse Analytics, Azure SQL Database, SQL Server, Azure SQL Managed Instance, and Amazon RDS for SQL Server connectors in Azure Data Factory and Azure Synapse
This article provides suggestions to troubleshoot common problems with the Azure Synapse Analytics, Azure SQL Database, and SQL Server connectors in Azure Data Factory and Azure Synapse.
21
+
This article provides suggestions to troubleshoot common problems with the Azure Synapse Analytics, Azure SQL Database, SQL Server, Azure SQL Managed Instance, and Amazon RDS for SQL Server connectors in Azure Data Factory and Azure Synapse.
22
22
23
23
## Error code: SqlFailedToConnect
24
24
@@ -33,7 +33,7 @@ This article provides suggestions to troubleshoot common problems with the Azure
33
33
| If the error message contains the string "SqlException", SQL Database the error indicates that some specific operation failed. | For more information, search by SQL error code in [Database engine errors](/sql/relational-databases/errors-events/database-engine-events-and-errors). For further help, contact Azure SQL support. |
34
34
| If this is a transient issue (for example, an instable network connection), add retry in the activity policy to mitigate. | For more information, see [Pipelines and activities](./concepts-pipelines-activities.md#activity-policy). |
35
35
| If the error message contains the string "Client with IP address '...' is not allowed to access the server", and you're trying to connect to Azure SQL Database, the error is usually caused by an Azure SQL Database firewall issue. | In the Azure SQL Server firewall configuration, enable the **Allow Azure services and resources to access this server** option. For more information, see [Azure SQL Database and Azure Synapse IP firewall rules](/azure/azure-sql/database/firewall-configure). |
36
-
|If the error message contains `Login failed for user '<token-identified principal>'`, this error is usually caused by not granting enough permission to your service principle or system-assigned managed identity or user-assigned managed identity (depends on which authentication type you choose) in your database. |Grant enough permission to your service principle or system-assigned managed identity or user-assigned managed identity in your database. <br/><br/> **For Azure SQL Database**:<br/> - If you use service principle authentication, follow [Service principal authentication](connector-azure-sql-database.md#service-principal-authentication).<br/> - If you use system-assigned managed identity authentication, follow [System-assigned managed identity authentication](connector-azure-sql-database.md#managed-identity).<br/> - If you use user-assigned managed identity authentication, follow [User-assigned managed identity authentication](connector-azure-sql-database.md#user-assigned-managed-identity-authentication). <br/> <br/>**For Azure Synapse Analytics**:<br/> - If you use service principle authentication, follow [Service principal authentication](connector-azure-sql-data-warehouse.md#service-principal-authentication).<br/> - If you use system-assigned managed identity authentication, follow [System-assigned managed identities for Azure resources authentication](connector-azure-sql-data-warehouse.md#managed-identity).<br/> - If you use user-assigned managed identity authentication, follow [User-assigned managed identity authentication](connector-azure-sql-data-warehouse.md#user-assigned-managed-identity-authentication).<br/> <br/>**For Azure SQL Managed Instance**: <br/> - If you use service principle authentication, follow [Service principal authentication](connector-azure-sql-managed-instance.md#service-principal-authentication).<br/> - If you use system-assigned managed identity authentication, follow [System-assigned managed identity authentication](connector-azure-sql-managed-instance.md#managed-identity).<br/> - If you use user-assigned managed identity authentication, follow [User-assigned managed identity authentication](connector-azure-sql-managed-instance.md#user-assigned-managed-identity-authentication).|
36
+
|If the error message contains `Login failed for user '<token-identified principal>'`, this error is usually caused by not granting enough permission to your service principle or system-assigned managed identity or user-assigned managed identity (depends on which authentication type you choose) in your database. |Grant enough permission to your service principle or system-assigned managed identity or user-assigned managed identity in your database. <br/><br/> **For Azure SQL Database**:<br/> - If you use service principle authentication, follow [Service principal authentication](connector-azure-sql-database.md#service-principal-authentication).<br/> - If you use system-assigned managed identity authentication, follow [System-assigned managed identity authentication](connector-azure-sql-database.md#managed-identity).<br/> - If you use user-assigned managed identity authentication, follow [User-assigned managed identity authentication](connector-azure-sql-database.md#user-assigned-managed-identity-authentication). <br/> <br/>**For Azure Synapse Analytics**:<br/> - If you use service principle authentication, follow [Service principal authentication](connector-azure-sql-data-warehouse.md#service-principal-authentication).<br/> - If you use system-assigned managed identity authentication, follow [System-assigned managed identities](connector-azure-sql-data-warehouse.md#managed-identity).<br/> - If you use user-assigned managed identity authentication, follow [User-assigned managed identity authentication](connector-azure-sql-data-warehouse.md#user-assigned-managed-identity-authentication).<br/> <br/>**For Azure SQL Managed Instance**: <br/> - If you use service principle authentication, follow [Service principal authentication](connector-azure-sql-managed-instance.md#service-principal-authentication).<br/> - If you use system-assigned managed identity authentication, follow [System-assigned managed identity authentication](connector-azure-sql-managed-instance.md#managed-identity).<br/> - If you use user-assigned managed identity authentication, follow [User-assigned managed identity authentication](connector-azure-sql-managed-instance.md#user-assigned-managed-identity-authentication).|
0 commit comments