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!The Power BI Data Visualization World Championships is back! It's time to submit your entry. Live 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!
The Power BI Data Visualization World Championships is back! It's time to submit your entry.
Check out the January 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 60 | |
| 41 | |
| 27 | |
| 25 | |
| 23 |
| User | Count |
|---|---|
| 127 | |
| 109 | |
| 55 | |
| 39 | |
| 33 |