Lakehouse configuration suggestions · Learn Microsoft Fabric

Lakehouse configuration suggestions

We have a very small team that's handling the data and reporting for our group of companies. We have several different applications that needs to be reported on individually and related to each other. With the idea that we're going to present the reporting through an App, how would you handle the Lakehouse(s)?

At the Gold level, is it better to have a separate Lakehouse per application in order to clearly separate the tables and use linked tables to create the joined model(s), or just have it all in a single Lakehouse with a clear naming convention and multiple models?

8 comments