Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowData Days is here! Join us now for 60+ days of learning, challenges, and connection. Learn more
Hi community,
we have our sales data and employee working hours in MySQL tables. I import this data and transform it for Power BI using Power Query. However, this process now takes several hours, which leads to a timeout during the dataset refresh in Power BI online.
What would you suggest? Should I perform the data processing beforehand, e.g., using a PHP script, and make the prepared data available in a new MySQL table for Power BI? What is the best practice here?
Thanks for your help!
Steffen
Solved! Go to Solution.
Hi @SteffenH82
I would recommend preparing the data as much as possible at the source. Power Query is powerful, but many transformations on big datasets can cause these issues. When connecting to the Database, you can use the Advanced Options to set a timeout
You will be probably aware, but I will mention it anyway. Try and keep the transaction tables as slim as possible, only have ids, dates etc in these tables. If the employee table has Date/Time columns, if you don't need the time, then convert to date only. If you do need the time, create a separate column for the time part. The more cardinality in the columns the faster the load. Move all teh information like products, employee, date, time infomation etc.. to dimension tables. More info here
In the options section of Power BI Desktop, you can set some settings to help with loading times. Turn off Time intelligence if you are using a date table.
Hope these tips help
Joe
Proud to be a Super User! | |
Date tables help! Learn more
Hi @SteffenH82
I would recommend preparing the data as much as possible at the source. Power Query is powerful, but many transformations on big datasets can cause these issues. When connecting to the Database, you can use the Advanced Options to set a timeout
You will be probably aware, but I will mention it anyway. Try and keep the transaction tables as slim as possible, only have ids, dates etc in these tables. If the employee table has Date/Time columns, if you don't need the time, then convert to date only. If you do need the time, create a separate column for the time part. The more cardinality in the columns the faster the load. Move all teh information like products, employee, date, time infomation etc.. to dimension tables. More info here
In the options section of Power BI Desktop, you can set some settings to help with loading times. Turn off Time intelligence if you are using a date table.
Hope these tips help
Joe
Proud to be a Super User! | |
Date tables help! Learn more
Don't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.
Check out the May 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 16 | |
| 10 | |
| 10 | |
| 8 | |
| 7 |
| User | Count |
|---|---|
| 41 | |
| 36 | |
| 34 | |
| 28 | |
| 20 |