Generic Error output of Snowflake V2 Connector

Question

The new Snowflake V2 connector is giving a constant error output when the copy activity fails i.e.

Failed to execute script. Exception: 'Failed to open the database connection.

The Snowflake Legacy connector atleast used to provide us some details on the error, like database doesn't exists or invalid warehouse.

As a result with this new connector our lives are becoming very difficult to debug upon errors. Can we please have back the property of giving back the detailed error.

Answer 1

Hello Swapnil Sarkar,

Welcome to the Microsoft Q&A forum.

Based on the error message "Failed to execute script. Exception: 'Failed to open the database connection." indicates that the script was unable to establish a connection to the database.

Can you please try the below and see if it helps resolve the issue.

1. Check the connection string: Make sure that the connection string used in the copy activity is correct and contains the necessary information such as server name, database name, user name, and password.
2. Check the firewall settings: Make sure that the IP address of the Azure Data Factory integration runtime is added to the Snowflake account firewall settings. You can find the IP address of the integration runtime in the Azure portal.
3. Check the user/role permissions: Make sure that the user/role used in Azure Data Factory has the necessary permissions to access the Snowflake database. You can check the permissions in the Snowflake web interface.
4. Check the Snowflake service status: Check if there are any issues with the Snowflake service status. You can check the status in the Snowflake web interface or by using the Snowflake command-line interface.

Additionally, please log a feedback item regarding the lack of detailed error messages in the Snowflake V2 connector on the ADF feedback channel:

Please do share the feedback link once it is posted so that we can share the info with respective product team. All the feedback logged in this forum are actively monitored and reviewed by respective engineering team and will consider during future implementations.

https://feedback.azure.com/d365community/forum/1219ec2d-6c26-ec11-b6e6-000d3a4f032c

Hope this helps. Do let us know if you any further queries.