Forum Discussion
Snowflake cloud connection: KeyPair authentication
Hi to all,
Quick update on this issue (Key-Pair authentication between Snowflake and Power BI).
Finally got a “solution” from the support and was able refresh the model using Key-Pair authentication.
What I ended up doing is to enable “Use legacy Snowflake connector implementation” within Preview features.
According to Microsoft support: “Currently, Implementation 2.0 consumes more memory, which the engineering team is actively working to optimize. This issue has been documented in the reference document below, and the document will be updated once the fix is implemented and released”.
Thank you.
Hi ustas55 ,
I am also facing similar errors (resource related as well) with our dataflow (gen 1) using the key pair auth, but runs fine when we switched back to username / password auth.
Something we noticed is that with the key pair auth , there are additional "junk queries" in Snowflake , e.g. SHOW queries like SHOW PRIMARY KEYS, SHOW COLUMNS ,etc...) instead of just a SELECT statement.
Do check your SNOWFLAKE query history on the account , it might be why it is using more memory than usual.
Thank you diabb8899,
Yes, that's exactly what I see in the Snowflake as well; junk queries with “Show Primary Keys”, “Show Columns”, and “Show Parameters like ODBC”. I guess it’s all part of the query building/validation activities passed from Power BI (model) to the Snowflake. But I would not expect those extra queries, which generate metadata, would increase memory size from 3 Gg to 20 Gb.
Hi ustas55 , contact MS Support and it is apparently a known and on-going issue with the Snowflake connector.
Replies from MS Support:
Feedback from the Product Team regarding this issue. Key-pair authentication is supported only with implementation 2.0. If the user does not explicitly specify an implementation, the connector defaults to 1.0 with username/password and automatically switches to 2.0 when key-pair authentication is selected. In general, the Snowflake connector using implementation 2.0 has the following characteristics: The overall load time is typically faster using Implementation="2.0", but the memory consumption can also be higher.There still doesn't seem to have any resolution to the issue yet, I am still pending MS Suport on that.