Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Learn more

Reply
katybr
Frequent Visitor

Data model

Hello! 

 

I have a question to know which is the best practice. 

I have a project where I have 4 tables:

-Program (IdProgram,Name,Responsable...)
-Parts of the program (IdProgram,IdSection,SectionName...)

-Parts (IdSection,IdParts,Description...)

-Conformities(IdParts,IdConformities,Answer..)

 

I can work with all those 4 tables related in the data model, each table have one columns that can be related with another table.

 

My question is, is it best to work with the 4 table separately or merge all the 4 tables into one?

 

Thank you 🙂

1 ACCEPTED SOLUTION
PaulDBrown
Community Champion
Community Champion

Best practices suggest creating dimension tables with unique values for fields common to different tables, creating one-to-many (single direction) relationships between these dimension tables and the corresponding fields in the fact tables. 
you then use the diemnsion table fields in measures, slicers, visuals, filters...
The dimension tables provide the filter context for correct filtering and calculations





Did I answer your question? Mark my post as a solution!
In doing so, you are also helping me. Thank you!

Proud to be a Super User!
Paul on Linkedin.






View solution in original post

2 REPLIES 2
PaulDBrown
Community Champion
Community Champion

Best practices suggest creating dimension tables with unique values for fields common to different tables, creating one-to-many (single direction) relationships between these dimension tables and the corresponding fields in the fact tables. 
you then use the diemnsion table fields in measures, slicers, visuals, filters...
The dimension tables provide the filter context for correct filtering and calculations





Did I answer your question? Mark my post as a solution!
In doing so, you are also helping me. Thank you!

Proud to be a Super User!
Paul on Linkedin.






Anonymous
Not applicable

@katybr Hi, I don't have much details about your model, but it's depend on each table's complexity and weight. Also I believe if you merge 4 queries in one, it wouldn't be good practice in term of query performance. 

Helpful resources

Announcements
Fabric Data Days Carousel

Fabric Data Days

Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!

October Power BI Update Carousel

Power BI Monthly Update - October 2025

Check out the October 2025 Power BI update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors