Forum Discussion
Data connection issues with Google Big query
- 1 year ago
We found that problem. We haven't found the solution to the problem while using the new ADBC connector. If ADBC is disabled it uses ODBC and works again. Can enable/disable here: To access this feature in Power BI Desktop, navigate to Options and settings (under the File tab) > Options > Preview features, and then select the checkbox to enable the Use new Google BigQuery connector implementation option. Once the option is on, all the newly created connections automatically use the new connector implementation.
We found that problem. We haven't found the solution to the problem while using the new ADBC connector. If ADBC is disabled it uses ODBC and works again. Can enable/disable here: To access this feature in Power BI Desktop, navigate to Options and settings (under the File tab) > Options > Preview features, and then select the checkbox to enable the Use new Google BigQuery connector implementation option. Once the option is on, all the newly created connections automatically use the new connector implementation.
- naphob1 year agoRegular Visitor
Hello agomez_binni Thank you for suggesting an alternative method, this method worked for me as I updated Power BI desktop version and disable this Preview Feature.
- v-hashadapu1 year ago
Community Support
Hi naphob , thanks for the update, glad it worked. If you have any other queries, please feel free to create a new post in the community. We are always happy to help.
- Suu1 year agoFrequent Visitor
any solution for Dataflow? I found that I can only use existing Table/View from BigQuery but cannot use SQL Query in the new connector. Thanks!
- v-hashadapu1 year ago
Community Support
Hi Suu , Thank you for reaching out to the Microsoft Community Forum.
In Power BI Dataflows (and Fabric Dataflows Gen2), the new Google BigQuery ADBC connector doesn’t support custom SQL queries, it only lets you pull from existing tables or views. That’s why you can’t paste a query directly like in Power BI Desktop with the older ODBC connector. The workaround is to create a view in BigQuery that contains your SQL logic, then point your Dataflow to that view. This way you get the same result while staying within the connector’s current limitations.