Forum Discussion
Should I query once and reference or split my table
Hi, Anonymous
Generally, It is recommended that you reference queries to avoid the duplication of logic across your queries. However, this design approach can contribute to slow data refreshes, and overburden data sources. Consider several queries: Query1 sources data from a web service, and its load is disabled. Query2, Query3, and Query4 all reference Query1, and their outputs are loaded to the data model. When the data model is refreshed, it's often assumed that Power Query retrieves the Query1 result, and that it's reused by referenced queries. This thinking is incorrect. In fact, Power Query executes Query2, Query3, and Query4 separately.
For further information, you may refer to the following link.
https://docs.microsoft.com/en-us/power-bi/guidance/power-query-referenced-queries
https://docs.microsoft.com/en-us/power-bi/power-bi-reports-performance
Best Regards
Allan
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Community SupportHi, Anonymous
Generally, It is recommended that you reference queries to avoid the duplication of logic across your queries. However, this design approach can contribute to slow data refreshes, and overburden data sources. Consider several queries: Query1 sources data from a web service, and its load is disabled. Query2, Query3, and Query4 all reference Query1, and their outputs are loaded to the data model. When the data model is refreshed, it's often assumed that Power Query retrieves the Query1 result, and that it's reused by referenced queries. This thinking is incorrect. In fact, Power Query executes Query2, Query3, and Query4 separately.
For further information, you may refer to the following link.
https://docs.microsoft.com/en-us/power-bi/guidance/power-query-referenced-queries
https://docs.microsoft.com/en-us/power-bi/power-bi-reports-performance
Best Regards
Allan
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
v-alq-msft that is great to know thanks. Sadly, it seems another team is working on datasets and I won't be able to try them out.
Do you think it's better to just cut my table into smaller parts then ?
- v-alq-msft
Hi, Anonymous
Scheduled refresh for imported datasets timeout after two hours. This timeout is increased to five hours for datasets in Premium workspaces. If you encounter this limit, consider reducing the size or complexity of your dataset, or consider breaking the dataset into smaller pieces. Thanks.
Best Regards
Allan