Custom schema and multipart naming in Microsoft Fabric Lakehouse

Lakehouse supports the creation of custom schemas. Schemas allow you to group your tables together for better data discovery, access control, and more. Historically, creating schemas was a privilege reserved for Data Warehouses, but now, schemas can be directly created within a Lakehouse environment too! This advancement unlocks new architectural opportunities, allowing for more organized, structured, and scalable data solutions within the Lakehouse. Embrace the flexibility and innovation of modern data management strategies!
Key Benefits:
Enhanced organization: easily categorize and manage your data within the Lakehouse.
Scalability: accommodate complex data models and extensive datasets.
Flexibility: implement diverse architectural patterns tailored to your needs.
How to enable schema support?
To enable schema support for your lakehouse, check the box next to Lakehouse schemas (Public Preview) when you create it.
Once you create the lakehouse, you can find a default schema named dbo under Tables. This schema is always there and can't be changed or removed. To create a new schema, hover over Tables, select …, and choose new schema. Enter your schema name and select Create. You'll see your schema listed under Tables in alphabetical order.
Docs: learn.microsof...
🎙 Meet the Speakers:
👤 Guest from Microsoft Fabric Product Group: Ted Vilutis: Senior Product Manager at Microsoft
LinkedIn: / tedvilutis
Twitter: / tvilutis
👤 Host: Estera Kot, PhD, Principal Product Manager at Microsoft
LinkedIn: / esterakot
Twitter: / estera_kot
👍 Like this video? Don't forget to hit the 'Like' button and share it with your network!

[@frizz-vb6ct]

Thanks for making these great videos! It's awesome to get in on the journey like this.
I wish you will start posting the release of these videos in the Microsoft Fabric subreddit. I think the videos will be hugely popular among the folks over there.

[@AzureSynapse]

Thank you for the feedback, we will definitely consider it.

[@tannguyen0175]

How to get list schemas in a lakehouse