TYSM for putting this out. I was struggling to stitch it all together by reading the documentation, but so many details were still unclear. Documentation is still written as if it were 1995, prioritizing exhaustiveness of option descriptions over clarity. Step-by-step tutorials like these are priceless and should be included by editors because it's a real pain in the butt to go through Russian doll documentation pages, get lost, and waste 6 hours of trial and error just to set up an option correctly.

Amazing man. Your explanation and demo are clear. Keep going don’t stop.

Great Explanation, clear and informative. Thank You.

Thanks a lot from sharing your knowledge

Great, thanks a lot! Very clear. If that's possible could you make a guide how to do all the deployments and enabling Unity Catalog using Terraform?

From Nov 2023, by default Azure is enabling all workspaces with Unity catalog, I saw it in MSft documentation

AMAZING THANK YOU BROTHER

Great video, thanks! I found various documents for different tasks mentioned here; but it was a pain to resolve what I was missing. Thanks to this video, I was able to find what I was missing. Is there a single Azure Databricks document that explains the whole flow?

Well Explained !! Very Useful. Kindly try to make the video bit clear vision. Thanks :)

Great, thanks!

Very helpful, thx!

Thank you so much...

Hey, Nice video, is it possible to use the access connector and datalake automatically created with workspace or we leave it alone and why?

That's for a really clear and straight forward tutorial. The one question that nagged me though (and you have may have touched on it, but I missed it), is why we are creating an additional storage account and account connector when one already appears to exist in the managed resource group that is generated when you created the initial premium workspace. I even saw in your tutorial when I re-watched it, the drop-down menus referenced the ones (storage account and access connector) that were already available in addition to the ones you created. Is there anything wrong with using the ones the Storage Account and Access Connector that were already created on your behalf as opposed to re-creating your own in order to enable UC? Or is it a best practice to create additional separate resources for UC enablement rather than using what exists?

How would this implementation play out when you need the underlying data to be stored across different environment locations? Like a dev/uat/prd? Creating the single metastore means that all underlying managed files are created in that one location. Would you skip providing the ADLS Gen 2 path (@ 9:57) and then provide each location when creating the catalog itself? That part is not clear to me...

Unity catalog can't be enabled for the hive_metastore, that's there by default?

This is amazing, end-end show of how this complex stuff works. Is this the same if we already have a databricks workspace (premium tier) with no Unit Catalog? 1. we just have to create Access Connector Resource object 2. Do the same steps as recommmended here. Kindly confirm.

nice video