This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
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
Check out the May 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 32 | |
| 25 | |
| 23 | |
| 22 | |
| 13 |
| User | Count |
|---|---|
| 62 | |
| 47 | |
| 27 | |
| 23 | |
| 19 |