The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends September 15. Request your voucher.
Hello:
This is the dataset example i got from excel. To make a data modelwhich field i need consider as dim and fact table?
Sourc_file | user_email | system_time stamp | tool Name |
\\abc | abc@xy.com | 9:02:12 AM | Formula |
\\abc | xyz@xy.com | 10:02:12 AM | Developer |
\\abc | tcx@xy.com | 11:02:12 AM | Python |
\\abc | lkj@xy.com | 12:02:12 PM | R |
Appreciate your help.
Thanks
Solved! Go to Solution.
As per standards the Dim table is the one where you have required dimensions for data analysis. While Fact table normally have corresponsing keys with Facts (measures in it). This looks insufficient data to decide but you can use email to derive Users Name and put in Dim Table and any count of column which makes meaningful data should work here.
Hope it helps.
Hi @nafric
A fact table stores measurable, usually, numeric data (sales, revenue, transaction volume) which may have a varying degree of granularity (transaction or line item level). A dimension table stores descriptive attributes (customer - customer location, customer email or product - product category, model, color, size, sku). Yours is a user dimension table containing user creation time (possibly) and dev roles.
As per standards the Dim table is the one where you have required dimensions for data analysis. While Fact table normally have corresponsing keys with Facts (measures in it). This looks insufficient data to decide but you can use email to derive Users Name and put in Dim Table and any count of column which makes meaningful data should work here.
Hope it helps.
User | Count |
---|---|
56 | |
54 | |
53 | |
47 | |
30 |
User | Count |
---|---|
175 | |
88 | |
69 | |
48 | |
47 |