Forum Discussion
Power ParticipantKusto Query Limits
Hi DennesTorres
Yes there are ways to deal with this with commands https://learn.microsoft.com/en-us/azure/data-explorer/kusto/concepts/query-limits#limit-on-result-set-size-result-truncation.
You can try like this:set notruncation;
MyTable | take 1000000
Even in Fabric, KQL DB automatically makes the data available in OneLake in delta format.Hi,
I think it worked.
It resulted in an error on the UI, but I believe it will work in othe places.Meanwhile I discovered the pipelien COPY activity ignores the Kusto query limit automatically, without the need of this set.
On the other hand, the dataflows gen 2 are tied with kusto limit, probably they will need this set.
Thank you!
Dennes
Hi DennesTorres
Thanks for using Fabric Community.
At this time, we are reaching out to the internal team to get some help on this. We will update you once we hear back from them.
Thanks
Hi DennesTorres
Yes there are ways to deal with this with commands https://learn.microsoft.com/en-us/azure/data-explorer/kusto/concepts/query-limits#limit-on-result-set-size-result-truncation.
You can try like this:
set notruncation;
MyTable | take 1000000
Even in Fabric, KQL DB automatically makes the data available in OneLake in delta format.
DennesTorresHi,
I think it worked.
It resulted in an error on the UI, but I believe it will work in othe places.Meanwhile I discovered the pipelien COPY activity ignores the Kusto query limit automatically, without the need of this set.
On the other hand, the dataflows gen 2 are tied with kusto limit, probably they will need this set.
Thank you!
Dennes