Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Learn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
Hi,
I am working with our DBA team to model one of our main fact data sources in our server, which is healthcare claim level data that goes to insurance payers. I am trying to see what the best practice is on how to store data like this for the best power bi performance:
This is how the table looks:
This is what I want it to look like so it can be a star schema and I can connect different dimension tables to it. The problem with this is that it can get into 100billion rows due to the row splits. Should I be worried about row count? If so, what is another way of doing it?
I would appreciate any best tips and best practices.
Thanks!
Try waterfall model for details review the following articles
Did I answer your question? If so, please mark my post as a solution!
Proud to be a Super User!
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 53 | |
| 48 | |
| 38 | |
| 15 | |
| 14 |
| User | Count |
|---|---|
| 93 | |
| 79 | |
| 37 | |
| 27 | |
| 25 |