Filtering and visualizing Kusto data in local time
Datetime values in Kusto (aka Azure Data Explorer/ADX/KQL database in Fabric) are assume to be in UTC time. In many cases users want to filter the data and see the results using their local time. This article compares different approaches to achieve this result and do it in an efficient way. The Kusto engine includes some new optimizations in this area but still caution is recommended. KQL examples that can be run on test data and are included also a paragraph and an example on how to implement in Power BIWhy 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.Near real time reports in PBI + Kusto
In some scenarios users want the PBI reports to refresh automatically without user interaction. It can be challenging for the PBI service and the Kusto backend to cope with a high volume of direct queries. In this article I'll suggest some ways to make the scenario pheasible.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.
