FAST - Billions of rows with Azure Data Explorer (ADX)

Поделиться
HTML-код
  • Опубликовано: 21 янв 2025

Комментарии • 28

  • @aaron6516
    @aaron6516 2 года назад +5

    Man this seems sick!!! Need to explore more... very cool thanks for sharing this!

  • @AkshayDixit
    @AkshayDixit 2 года назад +4

    This is so exciting!! Loved the energy!

  • @yihezkel
    @yihezkel 2 года назад +2

    Subscribed, glad I discovered this channel!
    Please do a deeper dive

  • @sau002
    @sau002 2 года назад +1

    Is there a very well tuned MS Sql under the hood ?

  • @yschuster
    @yschuster 2 года назад +2

    I love how you show the documentation! What a fun session :)

  • @jameshayes2941
    @jameshayes2941 2 года назад +3

    Love this. Wish I could play with this at work.

    • @SaeedCoptywho
      @SaeedCoptywho 2 года назад

      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

    • @rishirajdeb
      @rishirajdeb 2 года назад

      The free cluster is dedicated to only Microsoft employees as they mentioned :(

  • @Bharath_PBI
    @Bharath_PBI 2 года назад +3

    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..

    • @SaeedCoptywho
      @SaeedCoptywho 2 года назад

      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

    • @SCoetzer
      @SCoetzer 2 года назад

      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

  • @rickmarciniak2985
    @rickmarciniak2985 2 года назад +1

    Way above my pay-grade but very interesting to say the least. KSQL..?

  • @sau002
    @sau002 2 года назад +1

    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.

  • @marcomacca5839
    @marcomacca5839 2 года назад +5

    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.

    • @Bharath_PBI
      @Bharath_PBI 2 года назад +1

      Good to know 👍

    • @SaeedCoptywho
      @SaeedCoptywho 2 года назад +1

      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)

    • @marcomacca5839
      @marcomacca5839 2 года назад

      @@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. ;)

    • @SaeedCoptywho
      @SaeedCoptywho 2 года назад +1

      @@marcomacca5839 sure contacting you there

  • @fallinginthed33p
    @fallinginthed33p 2 года назад +3

    ADX is a few orders of magnitude faster than DAX 😅

    • @FajardoCtba
      @FajardoCtba 2 года назад +1

      I wish it is true! And Kusto to be as flexible as DAX

    • @Bharath_PBI
      @Bharath_PBI 2 года назад +1

      😂😂, then power BI users switching to adx , scraping PBI, cos adx is free with production instance.

  • @Imperatorius45
    @Imperatorius45 2 года назад

    Slow down microsoft, I can't keep up lol

  • @davidovic4845
    @davidovic4845 2 года назад

    Damn bro those queries were cached as fuck

    • @Bharath_PBI
      @Bharath_PBI 2 года назад

      You got it 👍

    • @danyhoter2240
      @danyhoter2240 2 года назад +2

      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.

    • @uribarashkusto6620
      @uribarashkusto6620 2 года назад

      Wanna bet?

  • @vishalnasre1251
    @vishalnasre1251 2 года назад

    This is insane