Azure Purview - Understanding the Elastic Data Map

Поділитися
Вставка
  • Опубліковано 5 жов 2024

КОМЕНТАРІ • 8

  • @darthhemi1735
    @darthhemi1735 2 роки тому +2

    So we basically get 300$ for the Data map, and 141$ a month for resource set... plus the "scanning cost" pay as you go(shouldnt be alot). so 450$ a month(this is what the pricing estimator shows up with) or 374 UK lbs... the Resource set is for scanning the data lake?

  • @ruchibigdata1784
    @ruchibigdata1784 3 роки тому

    Always Excited to see your new video. Thanks

  • @ramkipalle6612
    @ramkipalle6612 3 роки тому +2

    What is this ridiculous fascination for Microsoft to combine compute and storage together to come up with pricing? Why cannot they price storage and throughput separately? That way a customer can pay for storage all the time and only pay for the throughout whenever they use compute (Storage is much cheaper than compute). It also allows the customers to independently scale the storage and throughput.

  • @ChristianEdsbergMllgaard
    @ChristianEdsbergMllgaard 3 роки тому +1

    New security management looks cool.
    I guess we wont be able to manage Databricks table access through it?

    • @AdvancingAnalytics
      @AdvancingAnalytics  3 роки тому

      Nope, just controls permissions to read the purview assets. You could potentially build something that syncs purview objects with table access control lists, but would likely take a few leaps & workarounds!

    •  3 роки тому

      But as far as I remember there is a goal to introduce policies and manage security of external sources trough Purview, but we need to wait for that.

    • @ramkipalle6612
      @ramkipalle6612 3 роки тому

      I am looking forward to see the integration between Azure Purview and Databricks Unity data catalog.

  • @gauravkumar796
    @gauravkumar796 3 роки тому

    Haha ... I just deleted my old purview account which was so expensive... And created new one :) thank you