Visual initial loading time retrieval

Hi CU08101843,

I think the key point is that your test already tells you where the problem is. With the relationship inactive the visuals load in 3 seconds, so the cost comes from the join that DirectQuery generates when the relationship is active, not from the measures.

In DirectQuery every visual sends SQL to the source, and an active relationship turns into a join in that SQL. If Power BI cannot assume the keys always match, it uses outer joins, which are much heavier on a large table. You do not need to touch the DAX or the queries to improve that. The relationship setting is described in the Assume referential integrity documentation

The setting only helps if it is true, meaning every row on the many side has a matching key on the one side. It is also worth checking that both tables come from the same source, because a relationship across two different sources cannot be pushed down as a single join. To see the SQL that is sent, run Performance Analyzer and look at the query for the slow visuals, as described in the Performance Analyzer documentation

So I would work through it in this order

1. Performance Analyzer -> copy the query of the slow visual
2. Relationship -> Assume referential integrity (if the data allows it)
3. Source database -> index the join key columns
4. Both tables in the same source -> join is pushed to SQL
Active relationship -> JOIN in the SQL -> 1 minute
Inactive relationship -> no JOIN -> 3 seconds

Please also test it with a quick change first. Turn on Assume referential integrity on a copy of the file, and compare the Performance Analyzer duration for those same three visuals. If the source has an index on the key columns, the improvement is usually visible straight away.

So I would start with the relationship setting and the indexes, because neither of them needs a change to the DAX or the DirectQuery source. Please let us know the result and mark a reply as the solution if it helps.

AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.