This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
Looking to see if anyone can provide some insight into this issue. I noticed a discrepancy between the distinct count function in Power BI and Kusto. Distinct Count in Power BI seems to have a threshold where afterwards, the result becomes an approximation/estimate.
As an example, I'm using a Kusto Query as my data source:
Table_Name | where Status == "Success" and Timestamp<=todatetime("7-6-2018") and Timestamp>=todatetime("6-7-2018") | project Column1, Column2, Timestamp | top 12647 by Timestamp
When I'm using the distinct count function to get the number of distinct Column1 (strings of numbers and letters), the result is 1024 (which is the correct value). When I increase the rowcount to 12648, the distinct count value drops to 1020.
For larger rowcounts, at times, the PowerBI result would be higher, at times lower.
EDIT: Should mention that I'm using DirectQuery instead of Import. Just tried on Import mode and this does not appear to be an issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.