Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Expert,
I need to merge two table both have record around 70,00,00. Have merge them using left outer join. But referesh is just keep on going and ultimately going for time out. Both Desktop and Dataflow is giving same issue.
Please suggest.
Thanks,
Girdhari
Solved! Go to Solution.
Hi @girdharimondal,
Merging 7 million rows with another large table will always be slow in Power BI. Here are couple of options you can try:
Best approach - Merge at the source:
If you must merge in Power BI:
Alternative architecture:
7M x 7M rows is beyond Power Query's best practise. You really need database-level joining.
Best regards!
PS: If you find this post helpful consider leaving kudos or mark it as solution
Hi girdharimondal,
We are pleased to learn that your issue has been resolved. Should you have any further queries, please feel free to contact the Microsoft Fabric community.
Thank you.
Thanks Everyone for your valuable response!
Was able fix the issue , it was actually a cardinality issue. I did not notice it, join was happening on M:M relation and that's why keep on exceuting . We have corrected the keys and everything is fine now
Regards,
Girdhari
Hello @girdharimondal
Below are a few things you can try!
Model instead of flatten
If the intent is to bring fields from one table into another for reporting, ask: can this be a relationship instead?
Build a star schema: one Fact table + Dimension tables with relationships. This avoids heavy merges in Power Query.
Filter and slim before you merge
Remove unneeded columns early (folded Remove Columns).
Filter rows down to the needed time window (folded Filter Rows).
Avoid transforming to Text keys, use Integer or Fixed Decimal keys if possible.
Common mistakes that kill performance
Steps before merge that break folding (e.g., custom row-level functions, some Add Column logic, unbuffered web/excel sources).
Merging on non-matching data types (Text vs Whole Number).
Unnecessary sorts.
Hi @girdharimondal , did you already try to buffer the two tables, that means simply adding the following step to both queries before your join step?
Table buffered = Table.Buffer(#<your last step>)
Thanks for your response, will check and come back.
Regards,
Girdhari
Hi @girdharimondal,
Merging 7 million rows with another large table will always be slow in Power BI. Here are couple of options you can try:
Best approach - Merge at the source:
If you must merge in Power BI:
Alternative architecture:
7M x 7M rows is beyond Power Query's best practise. You really need database-level joining.
Best regards!
PS: If you find this post helpful consider leaving kudos or mark it as solution
Thanks for your response, will check and come back.
Record count is 700K not 7M. It's should not be too much for power BI, I beleive.
Regards,
Girdhari
@girdharimondal
To improve performance and efficiency, I recommend optimizing the right-hand table before merging. Please selectively keep only the essential columns from that table, discarding any that are not needed for the join or final result. Merging all 700K rows with excessive columns may be causing overhead.
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 15 | |
| 9 | |
| 9 | |
| 9 | |
| 8 |