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 nowJuly 7 - July 17 | Round 2 of the Power BI Dataviz World Championships. Don't miss your chance! Learn more
First, let me say that many of the tables I intend to use are calculated tables and thus I cannot use M/PowerQuery to do my merging.
I am using the following the following DAX query to merge two tables:
why you cannot create the calculated tables in Power Query? Is it technical constraint, or a legacy setup?
This problem would be much easier in PowerQuery, you technically can do it in DAX, but I honestly believe that you shouldn't
The reason is because of performance issues. I am working with very unresponsive SQL tables and when attempting to merge tables, group by and create calculated columns I would often have to wait an hour for the program to finish each operation while using DAX to perform the same operation it took 5 minutes. Due to the complexity of the relationship I need to build between the tables, Power Query bogged down my report too much.
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
Join Data Days 2026: 60 days of free live/on-demand sessions, challenges, study groups, and certification opportunities.
| User | Count |
|---|---|
| 27 | |
| 23 | |
| 18 | |
| 18 | |
| 15 |
| User | Count |
|---|---|
| 54 | |
| 44 | |
| 42 | |
| 39 | |
| 36 |