Hi @Anonymous
Read microsoft documentation.
https://docs.microsoft.com/en-us/power-bi/desktop-directquery-about
When creating a report using a DirectQuery connection, follow this guidance:
Consider use of Query Reduction options: Power BI provides options in the report to send fewer queries, and to disable certain interactions that would result in a poor experience if the resulting queries take a long time to run. To access these options in Power BI Desktop, go to File > Options and settings > Options and select Query reduction.
Checking box selections on the Query reduction let you disable cross-highlighting throughout your entire report. You can also show an Apply button to slicers or filter selections. This approach lets you then make many slicer and filter selections before applying them. No queries are sent until you select the Apply button on the slicer. Your selections can then be used to filter the data.
These options apply to your report while you interact with it in Power BI Desktop. These options also apply when your users consume the report in the Power BI service.
Apply filters first: Always apply any applicable filters at the start of building a visual. For example, rather than drag in TotalSalesAmount and ProductName, then filter to a particular year, apply the filter on Year at the very start. Each step of building a visual sends a query. Although it's possible to then make another change before the first query has completed, this approach still leaves unnecessary load on the underlying source. By applying filters early, it generally makes those intermediate queries less costly. Also, failing to apply filters early can result in hitting the 1 million row limit.
Thanks & regards,
Pravin Wattamwar
www.linkedin.com/in/pravin-p-wattamwar
If I resolve your problem Mark it as a solution and give kudos.
