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
Hello All,
I have 3 tables being pulled from our database as views. I have used the three tables with relationships between them for a bit and am now trying to make them a bit less clunky to work with by making a Star Schema.
After creating dimension tables with keys back to my fact table I have created a monstronsity that loads significantly slower than my original tables.
Ex: Dim_table with 800 rows will load the entire dataset from each source table.
I read somewhere(can no longer find source), that there is a database side change that can be made to resolve this behavior.
Any help is appreciated.
@PBI_Rookie , if you bring in table in star schema from database with keys. It will work much faster
refer this : https://starschemaanalysis.blogspot.com/2013/08/creating-star-schema-from-single-table.html
In power Bi, it is a cost split. if you have a single key column in table(non numeric) you can have that, as long as it does not cause performance issue and force you have numeric key, that will increase load time.
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 |
|---|---|
| 57 | |
| 37 | |
| 34 | |
| 19 | |
| 17 |
| User | Count |
|---|---|
| 74 | |
| 70 | |
| 37 | |
| 35 | |
| 25 |