Switching the Data Source for an Existing Dashboard

Q&A
, , , , , , ,
1

Hi,

I currently have a payroll dashboard that uses MS SQL Server as the data source. We are planning to migrate the backend to MySQL, and I’d like to update the dashboard to use MySQL instead.

Could you please let me know if it’s possible to switch the existing dashboard’s data source from MS SQL to MySQL, and if so, what steps or best practices I should follow?

2

Hi @Narayana1

While I haven’t done cross database replacement, I have done a fair number of datasource replacements with new ones taking their place.

You can try the following:

  1. Create a new dataset on mySQL database
  2. In your analysis go to Data > datasets menu
  3. Against each dataset in the analysis you have the elipsis button.
  4. image
  5. For your SQL server based dataset click that button and select replace
  6. Select your mysql datasource and click OK
  7. You may be prompted if the column names differ between the two datasets and you may need to provide the appropriate mapping from the old to the new if there are differences

regards,
Giri

1 Like
3

Hi Giridhar,

Thanks for your response.

I was able to replace the SQL Server data source with the MySQL data source as you suggested. The replacement worked, but I noticed that many of my calculated fields are now missing or broken after the switch.

Is there any way to retain or migrate the calculated fields when replacing a dataset in Amazon QuickSight?
Or do we need to manually recreate/adjust all calculations after a data-source replacement?

Any guidance would be helpful.

Thanks,
Sathish

4

Hi @Narayana1 ,

Just checking back in since we haven’t heard from you in a bit. I wanted to see if the guidance shared earlier helped resolve your question, or if you found a solution in the meantime.

But to answer your latest question, calculated fields are not automatically retained when you replace a dataset (Replacing datasets - Amazon Quick). Sadly, you will need to create/adjust all your calculated fields.

If you still have any additional questions related to your initial post, feel free to share them. Otherwise, any update you’re able to provide within the next 3 business days would be helpful for the community.

Thank you

1 Like
5

Unfortunately you have fix them manually. That is my understanding

1 Like
6

Hi @Narayana1

I have replaced datasets where the source and target databases were same (mySQL). The calculated fields are retained without issues unless there is any change in column names etc.

I don’t know if changing from SQLServer to mySQL introduces any additional layer of complexity.

Can you share a few samples where things were broken so I can provide my feedback?

Regards,
Giri

7

Hi @Narayana1,

Since we haven’t received any further updates from you, I’ll treat this inquiry as complete for now. If you have any additional questions, feel free to create a new post in the community and link this discussion for context.

Thank you!