Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreWe've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. 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
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 55 | |
| 39 | |
| 35 | |
| 19 | |
| 17 |
| User | Count |
|---|---|
| 73 | |
| 70 | |
| 37 | |
| 35 | |
| 26 |