Databricks Unity Catalog assets types and operating model for metadata synchronization
The Databricks Unity Catalog integration for metadata uses a specific subset of asset types. All of these come out-of -the-box.
| Asset type | Description |
|---|---|
|
Technology Asset System![]() |
Executable software that you can buy commercially off the shelf (COTS), or build internally, to automate one or more business functions that help run a business smoothly and efficiently. Examples: CRM, ERP, EDW |
|
Technology Asset Database![]() |
A collection of data that is systematically organized or structured, to make it easy to create, update, and query the information. Examples: Ora_DGC_V45, SalesDB2020 |
|
Data Asset Schema Data Structure ![]() |
An asset that contains the location of specific data. It provides all the details that are required for setting up a connection to a database or server. |
|
Data Asset
Table Data Structure ![]() |
An implementation of data entities in columns and rows, in a given database system. It is the basic structure of a relational database. Examples: Account_tbl, CUST_ADDR |
|
Data Asset Column Data Element ![]() |
An atomic unit of data that can be stored in a database table. Examples: FST_NM, EMPID |
Databricks Unity Catalog operating model for metadata synchronization
Tip In the latest UI, you can also integrate Databricks AI models.
