Using .show queries to understand and optimize the KQL sent from PBI to Kusto
You use Kusto /ADX / KQL databases in Fabric with Power BI. You want to see the queries send to the backend from PBI and try to optimize the behavior. This article includes a query starting with the ".show queries" command that can help you identify the queries that need your attentionWhy are 273 queries needed to refresh one chart in Power BI ?
A real case from the field in which a huge number of queries were send to an ADX database for refreshing a single visual. The reason was a wrong choice of storage modes for dimension tables. Alternative solutions are suggested at the bottom of the article.Cross highlight when using direct query in PBI
The default behavior of Power BI is that every visual can filter any other visual. This is fine when the model is using import mode and all queries are very fast and cheap. With Direct Query we need to be much more careful about the number of queries generated and send to the backend source
