Forum Discussion
Kusto query limits
Hi stefanik ,
Could you kindly share some screessnhots around the issue please? This is not helping much.
Add error screesnhot as well which you are facing.
As far as I know, the default value (500000 rows or 64MB) is up to limit.
Best Regards,
Yuna
Thx for your reply.
In reality there isn't any error at all (or at least i'm not able to find it). No refresh error.
Simply, after the refresh, the number of rows are not that expected.
I run a Kusto query that return (from azure portal) 245K rows (this is another test case but the behaviour seems to be the same as my first post). The table in powerbi hold at max 32K rows!
Each row has a field for a stack trace string that could be big, and i point to the limit of 64MB as the source of the "problem".
If i use set truncationmaxrecords = 10000, the query correctly returns 10K (instead of 32K), but if i set a value greter that 64MB (like for instance 127000000 about 125MB) nothing happen: only 32K rows.
If you say the limit has to be intended as up limit (as test seems to show), there was my misunderstand about them.
I'm asking because from the doc you can see an example like this:
set notruncation;
MyTable | take 1000000
that let me think i can go above the defaults!
Thx
Stefanik
p.s even with set notruncation; -> 32K rows