Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Score big with last-minute savings on the final tickets to FabCon Vienna. Secure your discount

Reply
amilpbi
Frequent Visitor

Changing Data Source From AlloyDb to Big Query?

We have an old Report that uses GCP alloyDb database To Establish ODBC with PostgrSQL connector with a SQL query to fetch Data.
Can we Change the Data Source to Big Query that uses a Different SQL Query but results the same Data Table.
As the ODBC Method refreshes as long as the VM instance is running, given that its configured to Turn itself off every evening, I have to restart it every day. 
I belive this problem can be erased with Big Query but unsure if we can just change the source and still maintain Table relationship and All DAX still remain operating.

1 ACCEPTED SOLUTION
Ritaf1983
Super User
Super User

Hi @amilpbi 

If your tables in BigQuery have exactly the same structure as those from AlloyDB (same table names, column names, and data types), then in most cases, you should be able to swap the data source without breaking relationships or DAX measures.

To minimize issues, I recommend the following:

  1. Ensure schema consistency – Column names, data types, and table names must match exactly.

  2. Use “Transform Data” to replace the source in Power Query rather than re-importing everything – this way, the data model structure is preserved.

  3. Refresh carefully and test visuals and measures to confirm everything works as expected.

Also, switching from ODBC to BigQuery may significantly improve refresh reliability and performance, especially if the VM powering AlloyDB shuts down nightly.

If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly

Regards,
Rita Fainshtein | Microsoft MVP
https://www.linkedin.com/in/rita-fainshtein/
Blog : https://www.madeiradata.com/profile/ritaf/profile

View solution in original post

1 REPLY 1
Ritaf1983
Super User
Super User

Hi @amilpbi 

If your tables in BigQuery have exactly the same structure as those from AlloyDB (same table names, column names, and data types), then in most cases, you should be able to swap the data source without breaking relationships or DAX measures.

To minimize issues, I recommend the following:

  1. Ensure schema consistency – Column names, data types, and table names must match exactly.

  2. Use “Transform Data” to replace the source in Power Query rather than re-importing everything – this way, the data model structure is preserved.

  3. Refresh carefully and test visuals and measures to confirm everything works as expected.

Also, switching from ODBC to BigQuery may significantly improve refresh reliability and performance, especially if the VM powering AlloyDB shuts down nightly.

If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly

Regards,
Rita Fainshtein | Microsoft MVP
https://www.linkedin.com/in/rita-fainshtein/
Blog : https://www.madeiradata.com/profile/ritaf/profile

Helpful resources

Announcements
August Power BI Update Carousel

Power BI Monthly Update - August 2025

Check out the August 2025 Power BI update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

Find out what's new and trending in the Fabric community.