Forum Discussion
STAR Schema filter DIM table by FACT Table
It has contract dates meaning it actually has a mapping to every row in all FACT tables.
I found a solution, I just did some SQL INNER JOINS with view of my FACT table. Unfortunatelly I wasn't able to replicate that in Power Query (Using merge queries, filter rows, they all failed either because of working with on-prem data or just timeout out after few hours).
Shame it has to be done via SQL in the source, not in PQ.
Please define "super huge" - how many rows (distinct values in [DIM_HDR_KEY])? Is it a true dimension table or can it be further normalized? Have you considered using incremental refresh?
This DIM table itself takes 40% of my model size according to DAX studio, about 5gb of size itself, 11mln rows. I don't think incremental refresh helps me as I need to see the preview to do further transofrmations in PQ view.
What is the purpose of that table? What kind of data does it hold?
It has contract dates meaning it actually has a mapping to every row in all FACT tables.
I found a solution, I just did some SQL INNER JOINS with view of my FACT table. Unfortunatelly I wasn't able to replicate that in Power Query (Using merge queries, filter rows, they all failed either because of working with on-prem data or just timeout out after few hours).
Shame it has to be done via SQL in the source, not in PQ.