Forum Discussion
Advocate IPower BI desktop bug for Snowflake key Pair authentication
in Power BI even though we use the implementation=1.0 that supposed to execute the Query with ODBC driver we have seen when we use Key-pair authentication it by default execute the query as ADBC driver (Go).
6 Replies
- GeraldGEmerick
Memorable Member
sushovan93 See if you can use the following technique: Post | LinkedIn
- Ahmed-Elfeel
Super User
Hi sushovan93,
Look here if this could help you : Snowflake Connector - An existing connection was forcibly closed by the remote host
if this post helps, then I would appreciate a thumbs up and mark it as the solution to help the other members find it more quickly.
sushovan93I'm already trying that, and it does work for other autentication methods, Oauth and Snowflake authentication does recognize the connector changes I can easily make it to ADBC with implementation=2.0 and ODBC using implementation=1.0, only problem with the Key-Pair authentication it does not change the driver if we use the implementation = 1.0 still uses the ADBC driver.
And in that the new ADBC driver has memory issue with large data that is alrady a known issue.- Ahmed-Elfeel
Hi sushovan93,
The only way i see to bypass this (until this issue solve) is to
- set up a System DSN on your machine using the Snowflake ODBC driver
- In Power BI Desktop use the ODBC connector (not the Snowflake connector) and select your DSN
- This method will give you full control over the driver and has been a stable workaround for many
Also Try to raise a ticket for Microsoft Support Team
if this post helps, then I would appreciate a thumbs up and mark it as the solution to help the other members find it more quickly
- sushovan93
That could work but I dont want to go that long way where we can easily change it in the native connector. or if it cannot then microsoft should atleast update it in their documention for the connector.
