Unveiling the Secrets: External Tables vs. External Volumes in Azure Databricks Unity Catalog

While reviewing the Databricks documentation about Unity Catalog, I came across a concept that initially seemed a bit perplexing: the distinction between accessing data objects stored in our cloud storage using External Tables versus External Volumes. This inspired me to write an article exploring the different methods for accessing data from the enterprise data lake through Unity Catalog. In this article, I delve into various syntax and nuances, explaining how one can efficiently access the data, particularly for organizations that have already established a data lakehouse within their data lake. <img alt="" src="https://miro.medium.com/v2/resize:fit:432/0*ZQ7navmn3_7x2ytm" style="height:432px; width:432px" /> <h1>Prerequisites for working with External tables, Managed tables, External Volumes</h1> To create an external location, you must first establish a storage credential using the Databricks Access Connector. These steps are essential whether you are creating a Metastore or enabling Unity Catalog. <a href="https://afroinfotech.medium.com/unveiling-the-secrets-external-tables-vs-external-volumes-in-databricks-unity-catalog-d13bf187e5f0">Read More</a>