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! It's time to submit your entry. Live now!
Hi,
I would like to know the difference in terms of performance between relationships and merge when using direct query. Especially for 1-1 tables. When I load a visual in which I have merged certain fields in advance (basically folding it into a sql query), is there a difference in the query plan using this approach vs when I simply have the two tables in the model and set a relationship between them and add that related field?
With this I also wonder: what part of the query gets executed on load of the visual: is is the folded query and whatever it needs on the visuals (so adding relationships and calculations to the query), or always just what the visual needs regardless of what was set in terms of merges etc?
=> so for instance, if you merged two tables in advance, but the related merged field is not in the visual, does it get queried?
Thanks in advance
I would recommend you make extensive use of the Performance Analyzer and of DAX Studio. The Performance Analyzer will give you the exact query (or queries) that the visual produces, and DAX Studio lets you look at the Query plans in excruciating detail.
A visual will only ever fetch the columns it needs to render, never any other columns.
The Power BI Data Visualization World Championships is back! It's time to submit your entry.
Check out the January 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 56 | |
| 42 | |
| 40 | |
| 21 | |
| 20 |
| User | Count |
|---|---|
| 150 | |
| 106 | |
| 65 | |
| 36 | |
| 36 |