Forum Discussion

Baqa's avatar
Baqa
Frequent Visitor
1 month ago
Solved

Issue with MySQL ODBC 8.x/9.x Drivers During Power BI Semantic Model Refresh

Hi Microsoft Support,

We are using an on-premises data gateway with an ODBC connection to a MySQL database for our Power BI semantic model refreshes.

Currently, we are using the MySQL ODBC 5.3 ANSI Driver, and the semantic model refresh completes successfully without any issues.

However, when we upgrade to newer versions of the MySQL ODBC driver, such as MySQL ODBC 8.6 or MySQL ODBC 9.1, the semantic model refresh fails while fetching data. Reverting back to the MySQL ODBC 5.3 ANSI Driver resolves the issue immediately.

Could you please help us understand:

  • Is there any known compatibility issue between Power BI Gateway and the newer MySQL ODBC drivers (8.x/9.x)?

  • Are there any changes in the newer drivers that could cause semantic model refresh failures?

  • Does Microsoft officially recommend a specific MySQL ODBC driver version for Power BI Gateway?

  • Are there any gateway or ODBC configuration changes required when using the newer MySQL ODBC drivers?

We would appreciate any guidance on why the newer drivers fail while the legacy 5.3 ANSI driver works correctly.

Thank you.

Need Help
  • Tahreem24's avatar
    Tahreem24
    1 month ago

    Baqa ,

    1. Short term: stay on MySQL ODBC 5.3 ANSI — it's working, and there's no functional obligation to upgrade unless you have a security/EOL driver.
    2.  If you must upgrade (e.g., 5.3 is EOL/blocked), move to an 8.x/9.x driver but:
      Create a 64-bit System DSN on the gateway,
      Set SSL Mode appropriately, force CHARSET=utf8mb4,
      Ensure the DB user uses mysql_native_password (or fully configure SHA2 + SSL),
      Restart the gateway service, then re-test the semantic model refresh.
    3. Alternative: consider the MySQL connector (Connector/NET) in Power BI instead of generic ODBC — it's the more "native" path and sidesteps several ODBC driver-default issues.

3 Replies

  • Tahreem24's avatar
    Tahreem24
    Icon for Super User rankSuper User
    1 month ago

    Baqa ,

    1. Short term: stay on MySQL ODBC 5.3 ANSI — it's working, and there's no functional obligation to upgrade unless you have a security/EOL driver.
    2.  If you must upgrade (e.g., 5.3 is EOL/blocked), move to an 8.x/9.x driver but:
      Create a 64-bit System DSN on the gateway,
      Set SSL Mode appropriately, force CHARSET=utf8mb4,
      Ensure the DB user uses mysql_native_password (or fully configure SHA2 + SSL),
      Restart the gateway service, then re-test the semantic model refresh.
    3. Alternative: consider the MySQL connector (Connector/NET) in Power BI instead of generic ODBC — it's the more "native" path and sidesteps several ODBC driver-default issues.
  • v-sathmakuri's avatar
    v-sathmakuri
    Icon for Community Support rankCommunity Support
    1 month ago

    Hi Baqa ,

     

    Thank you for reaching out to fabric community.

     

    Could you please review the suggestion provided above and let us know if you have any further questions?

     

    Thanks!!

  • v-sathmakuri's avatar
    v-sathmakuri
    Icon for Community Support rankCommunity Support
    1 month ago

    Hi Baqa ,

     

    Could you please check the provided suggestions and let us know if you have queries.

     

    Thanks!!