Showing results for 
Search instead for 
Did you mean: 
Frequent Visitor

Data Modeling Large Number of Facts


Im working with healthcare data that is rolled up by day and unit inside of each individual hospital. It looks something like this:

DateUnitBeds FilledRNsBeds NeededCovid


I have two other dimension tables. A date dimension table and a hierarchy table that I use to drill down the fact table with. For example the client can drill down to a particular hospital or unit type with the hierarchy table. 

The issue is that I have 3 or 4 data sources each with 20-30 metrics. Im concerned that if I joined all of them together, my fact table would be 100+ columns wide and my data model would take forever to refresh. Should I join them all so that I have a true "star schema" data model or keep them split up in a "constellation" model. 

Responsive Resident
Responsive Resident

@hwr7dd - A star schema is always preferred in Power BI. My advice based on the info you've given would be to join them and then remove all columns that are not used in the reporting. There's always the temptation to keep columns you may need but I would advise to get rid of them until you actually need it. 

Frequent Visitor

Unfortunately this is the truncated model. We have well over 300 metrics that we "could" report on that have been left out. The model that needs to be developed is fairly specific to healthcare/IoT as it has an unusual amount of facts and a low amount of dimensions. 

Helpful resources

PBI User Groups

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group!

MBAS on Demand

2021 Release Wave 2 Plan

Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.

July 2021 Update 768x460.png

Check it out!

Click here to read more about the July 2021 Updates

Top Solution Authors
Top Kudoed Authors