Power Query and Creating Dimension Table Best Practice question

[troyhimes]

The method I commonly use to create a dimension table seems to me to be process intensive.  I'm wondering if there is a better technique.  I'm still learning but quite ignorant as to what power query processes take up unecessary memory/processing time.

I am commonly using 2 or 3 related fact tables (100,000 to 300,000 rows of data) and create dimension tables by referencing the 2 or 3 queries that are retrieving the fact table data and removing duplicates of whatever dimension column I'm interested in.  My thinking is that these some these dimension tables need to be dynamic based on the data so I can't create static dimension tables.

Is there a better way to accomplish this?

[troyhimes · Accepted solution]

Thanks @Idrissshatila  for the insight.  Unfortunately I don't have access to that particular data.

[Idrissshatila]

Hello @troyhimes ,

If you have access to the souce of the data and you can build the dimension tables there, then it would be a better option. like if the data is coming from a sql server, what you could do is build the dimension tables in sql as views and import them to power BI as seperate tables.

If you don't have access or its not possible to build it in the source then I would be building it the way you're doing it.

If I answered your question, please mark my post as solution, Appreciate your Kudos 👍

Follow me on Linkedin