Is it really used by customers Leaving synapse behind? Is it that efficient compared to cached data models in PBI? (Apart from storage limit, but when it comes to compression, vertipaq I believe has higher compression ratio) If Yes, would like to know the feedback of those customers using it, and giving production instance for free is definitely a marketing strategy. Any KQL users here..
Hi Bharath - please note that moving from a free cluster to a prod tier cluster means moving to a full fledged dedicated instance with much more compute and storage power, and this will require a billing account with Azure
What was the rationale behind developing a new language KQL? I would like to know the limitations of TSQL that warranted the development of a new query language.
I’m using it alongside pbi…. And I’m not that impressed if I have to be honest. Querying 3 millions row in direct query with just normal Kpi (count/distinct ecc.) take to long.
is this on a free cluster or a prod cluster ? make sure you are querying the data from the cached data ... I have not see anything faster thatn ADX when your data is on disk ( cached) ( disclaimer : I work for Microsoft Azure and use this daily)
@@SaeedCoptywho prod cluster and data from ssd. So I think hot path. If you can provide support send me your LinkedIn profile. thanks for your answer. ;)
There is no caching for the results unless you request it. All of these queries can return in a matter of few seconds. One of the "secrets" for this performance is very efficient parallelism. You can scale out to hundreds of machines in Azure.
Man this seems sick!!! Need to explore more... very cool thanks for sharing this!
This is so exciting!! Loved the energy!
Subscribed, glad I discovered this channel!
Please do a deeper dive
Is there a very well tuned MS Sql under the hood ?
I love how you show the documentation! What a fun session :)
Love this. Wish I could play with this at work.
get your free cluster and play around with it, even when it's free it's still sitting in a secure and private location in Azure
The free cluster is dedicated to only Microsoft employees as they mentioned :(
Is it really used by customers Leaving synapse behind? Is it that efficient compared to cached data models in PBI? (Apart from storage limit, but when it comes to compression, vertipaq I believe has higher compression ratio)
If Yes, would like to know the feedback of those customers using it, and giving production instance for free is definitely a marketing strategy. Any KQL users here..
Hi Bharath - please note that moving from a free cluster to a prod tier cluster means moving to a full fledged dedicated instance with much more compute and storage power, and this will require a billing account with Azure
I feel the same. Where is the visualization ? I doubt my client will be able the run queries like this ?
I don't understand the point
Way above my pay-grade but very interesting to say the least. KSQL..?
Kusto Query Language - KQL
What was the rationale behind developing a new language KQL? I would like to know the limitations of TSQL that warranted the development of a new query language.
I’m using it alongside pbi…. And I’m not that impressed if I have to be honest. Querying 3 millions row in direct query with just normal Kpi (count/distinct ecc.) take to long.
Good to know 👍
is this on a free cluster or a prod cluster ? make sure you are querying the data from the cached data ... I have not see anything faster thatn ADX when your data is on disk ( cached) ( disclaimer : I work for Microsoft Azure and use this daily)
@@SaeedCoptywho prod cluster and data from ssd. So I think hot path.
If you can provide support send me your LinkedIn profile.
thanks for your answer. ;)
@@marcomacca5839 sure contacting you there
ADX is a few orders of magnitude faster than DAX 😅
I wish it is true! And Kusto to be as flexible as DAX
😂😂, then power BI users switching to adx , scraping PBI, cos adx is free with production instance.
Slow down microsoft, I can't keep up lol
Damn bro those queries were cached as fuck
You got it 👍
There is no caching for the results unless you request it. All of these queries can return in a matter of few seconds.
One of the "secrets" for this performance is very efficient parallelism.
You can scale out to hundreds of machines in Azure.
Wanna bet?
This is insane