Forum Discussion

dgwilson's avatar
dgwilson
Resolver III
1 year ago
Solved

Snowflake Conector 2.0 Preview - January 2025

Asking here if anyone else has had issues testing the new Snowflake Connector in the January 2025 release of Power BI Desktop? Version: 2.139.1576.0 64-bit (January 2025) Link to documentation - ...
Need Help
Tips and Tricks
  • dgwilson's avatar
    dgwilson
    1 year ago

    Answering my own question here... The syntax seems a bit different to the doc.

    [Role=SF_Access_Role, Implementation="2.0"]

    This 
    Source = Snowflake.Databases(SF_Address,SF_Warehouse, Implementation="2.0", [Role=SF_Access_Role]),
    becomes
    Source = Snowflake.Databases(SF_Address,SF_Warehouse, Implementation="2.0", [Role=SF_Access_Role, Implementation="2.0"]),


    It seemed very slow initially to retrieve a simple data set.
    2nd go was quite fast. I'll have to try another table now... there may have been a background install maybe?

     

     

rbriga's avatar
rbriga
Impactful Individual
1 year ago

I had a major issue with the new Snowflake implementation.

It works fine in Desktop, but not in Service.

When using a native Snowflake query, I would get the expected number of rows, but with wrong data.

ID fields (long text strings) would replicate the same value on other, otherwise correct, rows.

Note that it's not row duplication. For example, suppose this is the correct query values:

Product_IDProduct_Name
aaaaaaaaaaaaaaApple
bbbbbbbbbbbbBannana
cccccccccccccccCereals
ddddddddddddDonut

 The Service refresh would return:

Product_IDProduct_Name
aaaaaaaaaaaaaaApple
bbbbbbbbbbbbBannana
bbbbbbbbbbbbCereals
bbbbbbbbbbbb

Donut

 

It was hard picking up the reason for this. Removing the Implementation="2.0" tag fixed the issue.

AntoineAB1's avatar
AntoineAB1
Frequent Visitor
1 year ago

Hello. I had the same issue and just found out it was coming from the parameter [Implementation="2.0"].

Any idea how to deactivate this default parameter?

  • dgwilson's avatar
    dgwilson
    Resolver III
    1 year ago

    If you do not want to use the v2 implementation by default - you are best to turn off the preview feature. Then for any given table, you will have to edit the M code in Power Query to remove the [Implementation="2.0"] parameter. That should make Power Query use the v1 connector.

    • AntoineAB1's avatar
      AntoineAB1
      Frequent Visitor
      1 year ago

      Thank you. that worked!

    • SUMESHKUMAR22's avatar
      SUMESHKUMAR22
      Helper IV
      1 year ago

      Hi dgwilson ,
      Im getting below error when I removed the 2.0 part from the power query.
      let
      Source = Snowflake.Databases("uyt10278.west-us-2.azure.snowflakecomputing.com","COMPUTED_WH"),
      XHANCE_OPTINOSE_Database = Source{[Name="XHANCE_OPTINOSE",Kind="Database"]}[Data],
      XHANCE_OPTINOSE_DEV__HARSHAD_PARDESHI_Schema = XHANCE_OPTINOSE_Database{[Name="XHANCE_OPTINOSE_DEV__HARSHAD_PARDESHI",Kind="Schema"]}[Data],
      FCT_MEDIA_KPIS_View = XHANCE_OPTINOSE_DEV__HARSHAD_PARDESHI_Schema{[Name="FCT_MEDIA_KPIS",Kind="View"]}[Data]
      in
      FCT_MEDIA_KPIS_View
      Error:

      DataSource.Error: ODBC: ERROR [HY000] [Microsoft][Snowflake] (4)
      REST request for URL *** failed: CURLerror (curl_easy_perform() failed) - code=60 msg='SSL peer certificate or SSH remote key was not OK'.

      Details:
      DataSourceKind=Snowflake
      DataSourcePath=uza80192.east-us-2.azure.snowflakecomputing.com;COMPUTE_WH

      OdrbcErrors=[Table]

      • AntoineAB1's avatar
        AntoineAB1
        Frequent Visitor
        1 year ago

        Hello,

        I'm not expert but that looks like some issue that people had with ZScaler? If your organization have ZScaler set up on your machines, you might want to look into the related topics.