Why 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.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 attentionSearch text in a Kusto/ADX table using any number of terms from Power BI
In a table we have a free text column. Our goal is to return rows in which the text includes a list of terms which are pieces of text surrounded by special characters like comma, parentheses, space etc. We don't have such a filter in PBI so we'll use combination of a KQL operator - has_any and the mechanism of M dynamic parameters.Using Dual Mode dimension in Power BI with ADX data
Dual mode provides the best of using import mode and Direct Query mode for dimensions in PBI By using dual mode, you can reduce significantly the number of queries sent to ADX from PBI. The queries that involve the large tables using Direct Query will still be running entirely in ADX.
