According to Microsoft documentation PowerBI BigQuery connector should use Storage Read API by default https://learn.microsoft.com/en-us/power-query/connectors/google-bigquery#unable-to-authenticate-with... . Google documentation says that it is alternative mechanism to BigQuery REST API and Jobs https://cloud.google.com/bigquery/docs/reference/storage#background .
However, even if PowerBI project is configured to use UseStorageApi=true at least first connection to the BigQuery dataset still tries to use REST API.
DataSource.Error: ODBC: ERROR [42000] [Microsoft][BigQuery] (100) Error interacting with REST API: Access Denied: Project test-cloud-billing: User does not have bigquery.jobs.create permission in project test-cloud-billing.
Details:
DataSourceKind=GoogleBigQuery
DataSourcePath=GoogleBigQuery
OdbcErrors=[Table]
Not sure if that's the way PowerBI data preview works or because of other reasons, but this produces two issues:
1) It negated usage of Storage Read API as a more performant option and incurrs BigQuery Job costs. For example, if BigQuery dataset has millions of rows first transfer is always performed via traditional REST API Jobs.
2) It requires additional BigQuery Job User permissions, which are not always available in fine grained environments.
IMHO, BigQuery should be fixed to use only Storage API if that is specified in the project.
mattlee
on:
“Add Value” in Textbox Not Visible in Dark Theme
on:
Bi Crashes on launch with (AS Process PID=XXXXXX H...
on:
Fix the Date function in DAX
on:
May 25 update for Snowflake Connector v2 has broke...
on:
Unable to open existing PBIP files