Summary

In this rather dense chapter, we learned how data assets in the data catalog are secured with the data security model. We learned how user-facing table access control allows for the fine-grained implementation of the data security model using familiar SQL security statements such as GRANT and REVOKE. We also learned how Data Explorer allows visual, UI-based implementations of the table access control. After that, we learned about the underlying mechanics of authorizing Databricks SQL to cloud storage to access the necessary database files. Finally, we learned about the next-generation data cataloging technology known as Unity Catalog and how it improves upon the security capabilities of table access control with Hive Metastore.

In the next chapter, we will move on to the Databricks SQL workbench itself. Though we introduced the SQL Editor as part of this chapter, we will take this further and see how the SQL Editor, Dashboard Builder, and Query tabs all come together as...