Forum Discussion
Can Power Query handle this much data?
Jkaelinwhat are your data types in your facts? i really dont see an issue in combining them if they are most numerical, why doing you just try and see what happens? essentially its mostly up to your machine. and obviously because this is in memory technology you want to make sure you standarize your data as much as possible , the less unique values you have the better in order to get the most compression. Start only with what you need rather than everything.
Data types are all whole numbers & decimals.
Is flattening okay? Sometimes I have to create a financial ratio such as Sales / Assets. Sales will be in fTable 1 and Assets in fTable 2. I must have this data already combined into ratio for me to calculate statistics on it, such as Top third, Middle third, etc.
I really appreciate your help & thank you!
Jkaelin like i said i dont think there is an issue with combining, as long as its all at the same grain it might even make sense to do so, its not your typical relational data, you have only separated it out due to source constraints, your fields are mostly numeric so no issue there, 300 000 is not a biggie. Denormalising makes sense but like i say take out everything you dont need. leave the dimension as a dimension and only combine the facts. with my limited knowledge of what you doing, i dont see an issue