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 nowThe Fabric community is upgrading! Read all of the details including the timeline and what you can expect. Learn more
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
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
| User | Count |
|---|---|
| 24 | |
| 22 | |
| 20 | |
| 18 | |
| 14 |
| User | Count |
|---|---|
| 44 | |
| 36 | |
| 23 | |
| 20 | |
| 20 |