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

Next up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now

Reply
akhaliq7
Post Prodigy
Post Prodigy

Creating numerical columns using a group by add to fact table or create as a dim table

i have been working in power bi for a while and got into the habit of keeping numerical information that is created using a group by seperate from my fact table and creating a relationship between both tables in pbi desktop. But as I have been gaining experience starting to realise this may not be the best solution instead it is best to do joins to the fact tables (using sql) and bring them in as one fact table. Dimensions should be kept for anything that can be called a category or a date table.

 

Can someone explain further 

1 ACCEPTED SOLUTION
lbendlin
Super User
Super User

It depends on the nature of your facts. For example if you have Orders and Shipments then you could theoretically keep them in the same fact table.   But if you have Sales and Quota then you cannot combine these facts, they have to stay separate.  And there should be NO link between the fact tables !!!

 

Another thing to consider is the size and growth characteristics of your fact tables. Some will be slow growing, others will keep growing massively every day and you will want to think about  partitions and aggregations etc.

 

Having numerical columns to link between facts and dimensions is considered good practice as it helps to improve the join performance.

View solution in original post

2 REPLIES 2
lbendlin
Super User
Super User

Think about the nature of your data. Dimensions are something you filter by. Facts are something you count/sum up.

 

Don't join tables just because you can.  Your data model needs to reflect the business problem you are trying to solve for.

lbendlin
Super User
Super User

It depends on the nature of your facts. For example if you have Orders and Shipments then you could theoretically keep them in the same fact table.   But if you have Sales and Quota then you cannot combine these facts, they have to stay separate.  And there should be NO link between the fact tables !!!

 

Another thing to consider is the size and growth characteristics of your fact tables. Some will be slow growing, others will keep growing massively every day and you will want to think about  partitions and aggregations etc.

 

Having numerical columns to link between facts and dimensions is considered good practice as it helps to improve the join performance.

Helpful resources

Announcements
New to Fabric survey Carousel

New to Fabric Survey

If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.

Join our Fabric User Panel

Join our Fabric User Panel

Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.

March Power BI Update Carousel

Power BI Community Update - March 2026

Check out the March 2026 Power BI update to learn about new features.