Databricks Unity Catalog: A Technical Overview

preview_player
Показать описание
Welcome to the first video of my Databricks Unity Catalog Series! Unity Catalog brings a new layer of data management and security to your Databricks environment, and with this technical overview, you’ll learn about these capabilities.

⌚Timestamps:
00:00 Introduction
00:17 What is Unity Catalog?
00:30 Before vs After Unity Catalog
02:01 Key Features of Unity Catalog
02:39 Administrative Roles in Unity Catalog
03:15 Unity Catalog Object Model
04:24 Unity Catalog Enabled Workspace Demo
04:50 Accessing the Account Console
06:21 Catalog Explorer
08:40 3 Level Namespace
09:55 Table Object Details
10:39 Unity Catalog Permissions
11:17 Assigning Workspaces access to Catalogs
12:19 Comments and Tags
12:40 Data Lineage
14:09 Delta Sharing
14:15 External Data
14:55 Non Unity Catalog Enabled Workspace Demo
16:50 Summary

🔗 Links and Documentation:

💻 Check out my Databricks courses on Udemy:
Рекомендации по теме
Комментарии
Автор

I appreciate how you present information using a slow, clear, controlled voice.

thisoldproperty
Автор

This is way better than official Databricks Academy courses. Thanks for sharing

kvin
Автор

Best preparation about unity catalog I've ever seen!

yunshi
Автор

Very well explained.
I was frustrated with only theory of the unity catalog

arshadnehal
Автор

Thanks it was Very well paced and explained

TomaszBI
Автор

Excellently explained. Thanks for this.

sudeepsays
Автор

Thanks for the good explanation and demo.

ibdallah
Автор

Nice Presentation. It is well organized and precise. Thank you for your work

mariappan
Автор

thanks for the demo, it was really helpfull

egi
Автор

If i can't see 'manage account', what can i do for that?

casaspecsa
Автор

the HR catalog, what path did u choose when you configured the managed location path?

mainuser
Автор

Amazing overview!😁 I could think of one drawback of unity here: say user1 has access to catalog1, workspace1 and workspace2 has access to catalog1 as well. That would mean that user1 now has access to workspace1 and workspace2. is that correct? If yes then is there anyway to prevent this?

avinkohale
Автор

Thanks for the demo. Btw if the table type is External, can we also see the lineage?

FerdiArduyanto-hrkw