Hi Team, We have BigQuery project/dataset for Dev...
# gooddata-cloud
g
Hi Team, We have BigQuery project/dataset for Dev and a different BigQuery project/dataset for production. I would like to switch our GD workspace's data source from dev to prod but will this break all the dashboards and visualizations? The tables and schema are identical between Dev and prod.
k
Good news — switching your data source from Dev to Prod should not break your dashboards and visualizations, as long as the tables and schema are truly identical between the two environments. Here's what the knowledge sources confirm: Why it won't break things: GoodData's LDM maps to table/schema names, not to the specific data source connection itself. If your Prod BigQuery project/dataset has the same table names and schema structure as Dev, the existing LDM, metrics, visualizations, and dashboards will continue to work after you re-point the workspace to the Prod data source. This scenario — switching a workspace to a different data source while keeping the same LDM — is a recognized and supported use case in GoodData. [Parent/Child datasource] How to make the switch: You can update the data source using the Python SDK via
create_or_update_data_source
, which allows you to re-point a workspace from one environment (e.g., Dev) to another (e.g., Prod). [Python SDK datasource] Important precautions: • After switching, verify the LDM dataset-to-table mappings are still correct (check the Data mapping tab for each dataset in the LDM modeler). [LDM schema mapping] • Clear the cache after the switch to ensure queries run against the new Prod source and you're not seeing cached Dev results. • Test in a staging environment first if possible, and use the Model changes / Impact Analysis tool in the LDM modeler to check for any unexpected dependencies before and after the switch. [Monitor Model Changes] In short: if the schemas are truly identical, the switch is safe and your dashboards and visualizations should remain intact. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups. 👀 Our Support team monitors all messages and will jump in if needed.
g
in the "How to make the switch" it mentions using the using the Python SDK which we are not familiar with. is there another way to make the switch?
j
Hi Greg, Yes, there is another way to switch the data source without using the Python SDK. You can do this directly in the GoodData user interface. Here are the steps: 1. Go to the workspace where you want to change the data source. 2. Navigate to theDatasection. 3. In theData Sourcestab, find the data source you want to change and click on it. 4. In the data source details, click on theEditbutton. 5. Update the connection details to point to your Prod BigQuery project/dataset. 6. ClickSave. Please note that you should have the necessary permissions to edit the data source. Also, remember to clear the cache after switching the data source to ensure that the queries run against the new Prod source and you're not seeing cached Dev results.
g
Thank you! I'll try it.