Best practice for organizing data objects using Unity Catalog

[ossinova]

I was wondering if there is a best practice or recommended way to organize data objects (tables) in Unity Catalog.

Following the medallion architecture, how should one organize and name these three namespaces:

• Catalog(s)
• Schema(s)
• Table(s)

Example:

• Catalog: environment specific (dev / test / prod)
• Schema: layer specific (bronze / silver / gold)
• Table: tablename (sourceX_employee)

Example2:

• Catalog: environment and source specific (dev_sourceX / test_sourceX / prod_sourceX)
• Schema: layer specific (bronze / silver / gold)
• Table: tablename (employee)

How are you organizing your tables?

[Kaniz · Accepted solution]

Hi @ossinova, This document provides an opinionated perspective on how to best adopt Azure Databricks Unity Catalog and Delta Sharing to meet your data governance needs.

[Anonymous]

Hi @Oscar Dyremyhr​ 

Hope all is well! Just wanted to check in if you were able to resolve your issue and would you be happy to share the solution or mark an answer as best? Else please let us know if you need more help. 

We'd love to hear from you.

Thanks!

[jose_gonzalez]

HI @Oscar Dyremyhr​ ,

Just a friendly follow-up. Did any of the responses help you to resolve your question? if it did, please mark it as best. Otherwise, please let us know if you still need help.

[Avvar2022]

In Real time do we have 1 meta store for PROD and NON-PROD ? if Yes in the backend there would be a one storage account (ADLS Gen2) > Container for all Environments.