Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Direct query in Power BI is realy slow. How I can optimise to make it perform better?
Solved! Go to Solution.
Hi @ManojkMann ,
1. The relational database source can be optimized in several ways, as described in the following bulleted list.
Optimize data source performance
2. A DirectQuery model can be optimized in many ways, as described in the following bulleted list
3. Optimize the report design:
4. The benefits of Import and DirectQuery models can be combined into a single model by configuring the storage mode of the model tables. The table storage mode can be Import or DirectQuery, or both, known as Dual. When a model contains tables with different storage modes, it is known as a Composite model. For more information, see Use composite models in Power BI Desktop.
There are many functional and performance enhancements that can be achieved by converting a DirectQuery model to a Composite model. A Composite model can integrate more than one DirectQuery source, and it can also include aggregations. Aggregation tables can be added to DirectQuery tables to import a summarized representation of the table. They can achieve dramatic performance enhancements when visuals query higher-level aggregates. For more information, see Aggregations in Power BI Desktop.
Alternative, you can use the performance analyzer to exam report element performance Use Performance Analyzer to examine report element performance
Or the dax studio: Post
Also you can try to disable the options of type detection / relations in the Loading Data part.
File->Options->Current File->Data Load->Relationships
Turn off "Autodetect new relationship after data is loaded"
More blogs for reference:
Power BI query reduction when using DirectQuery
Best Regards,
Rico Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @ManojkMann ,
1. The relational database source can be optimized in several ways, as described in the following bulleted list.
Optimize data source performance
2. A DirectQuery model can be optimized in many ways, as described in the following bulleted list
3. Optimize the report design:
4. The benefits of Import and DirectQuery models can be combined into a single model by configuring the storage mode of the model tables. The table storage mode can be Import or DirectQuery, or both, known as Dual. When a model contains tables with different storage modes, it is known as a Composite model. For more information, see Use composite models in Power BI Desktop.
There are many functional and performance enhancements that can be achieved by converting a DirectQuery model to a Composite model. A Composite model can integrate more than one DirectQuery source, and it can also include aggregations. Aggregation tables can be added to DirectQuery tables to import a summarized representation of the table. They can achieve dramatic performance enhancements when visuals query higher-level aggregates. For more information, see Aggregations in Power BI Desktop.
Alternative, you can use the performance analyzer to exam report element performance Use Performance Analyzer to examine report element performance
Or the dax studio: Post
Also you can try to disable the options of type detection / relations in the Loading Data part.
File->Options->Current File->Data Load->Relationships
Turn off "Autodetect new relationship after data is loaded"
More blogs for reference:
Power BI query reduction when using DirectQuery
Best Regards,
Rico Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
72 | |
70 | |
37 | |
29 | |
26 |
User | Count |
---|---|
91 | |
49 | |
45 | |
38 | |
37 |