Fabric
12 TopicsTimespan/duration values in KQL, Power Query and Power BI
In many scenarios event durations are very important. They can be measured in days or in milliseconds and anything in between. In real time analytics it is especially important. In this article I'll describe how such values are treated in KQL and what happens to them when they are brought into Power Query and eventually to Power BI. Finally, I'll provide my recommendation for treating these values in Power BI.5.1KViews3likes0CommentsRelationships between ADX tables on two databases or two clusters
When using relationships between two ADX tables, we always prefer a join to be used between the two tables What if the two tables are not in the same database? This article will explain how to ensure proper joins are generated for these case.3KViews2likes0CommentsUsing .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 attention4KViews2likes0CommentsHow to use M dynamic parameters without most limitations
In the article and the example, I show how to feed more than one parameter from a single table and a single slicer. Selecting the values is done in a friendly way for the user, and a few more steps for the PBI developer.2.8KViews1like0CommentsHow many to many relationships affect the number of queries required to refresh matrices and tables
Relationships between tables coming from Kusto in direct query mode are created as M:M by default. Changing them 1:M can reduce the number of queries required for tables and especially matrices.3.3KViews1like0Comments