Upgrade to new Snowflake Linked Service, buggy with Source=mscorlib

Question

Hi, we recently upgraded our snowflake linked service to the newer version and once we released it to our production environment half of our activities started throwing

Failure happened on 'Source' side. 'Type=System.Exception,Message=[Snowflake] context canceled,Source=mscorlib,' errors.

I saw a similar issue with Salesforce here and the solution seemed to be force the linked service to not use v2 with this statement: "&feature.enableSalesforceV2=false". Is it the same statement we need to make with Snowflake "&feature.enableSnowflakeV2=false" and with the upcoming deprication of the old linked service will this still work after then or will this bug be fixed on it's own. We are using a self hosted IR.

Answer 1

Hello @Mike Fatal

Regarding your question, yes, you can try adding the statement "&feature.enableSnowflakeV2=false" to your linked service to force it to not use v2.

This should help resolve the issue you're experiencing with the "Source=mscorlib" error.

However, please note that this is just a temporary workaround and it's recommended to upgrade to the latest version of the Snowflake connector to avoid any potential issues in the future.

As for the upcoming deprecation of the old linked service, I'm not sure if this bug will be fixed on its own, but I recommend keeping an eye on any updates from Microsoft regarding this issue.

Lastly, since you're using a self-hosted IR, please make sure that the IR is also updated to the latest version to ensure compatibility with the latest Snowflake connector.

I hope this helps