Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hi,
i got some best practice design problems with my Data model, that consists of several fact and dimension tables. There is a screenshot with my current design considerations. I also thought about some possible solutions, but maybe you can help me to decide or give me some additional solutions/thoughts 🙂
1. Problem: try to avoid Snowflake-Hierachy because Star Schema seems to be best practice generally. In my case I need two identical Columns „Symbol“ in Dim_Symbol and Dim_Options. I need to show Option-Data from e.g. Fact_OptionTransactions also per Stock Symbol (e.g. how many Transactions for „AAP“)
2. Problem: Some calculated fields are needed as Dimension for filtering or in the legend of a visual. E.g. „Status“ of the trade (closed/open) or a Flag if it was a WinnerTrade. Further more there could be the same Trades (OptionNames) but from different Users.
3. Problem: What is the best way to implement RLS in my case?
Thank you very much!
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
114 | |
100 | |
81 | |
70 | |
62 |
User | Count |
---|---|
148 | |
116 | |
104 | |
90 | |
65 |