Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hi,
I am starting from scratch my dataset and have a common structure of:
since many years ago.
I was wondering if it makes sense to split those tables in two each, with current year on one table, and past years on another, so my refresh process would take much less data and time every day, as far as old data should never be updated.
On the other side, as order headers, delivery note headers and invoice headers are much smaller, I would keep one for each, for the whole years.
Daoes it make sense?
Thanks,
Solved! Go to Solution.
@jmvidal I am doing this with transaction data: 2015 to 2019 data is static and then 2020 data is refreshed. Then I use the UNION command. It makes the data refresh much faster.
Thanks, I''l be trying UNION.
Not a premium user yet.
I don't think that is the common practise. You might want to use aggregations if you have really large data sets though.
Thanks for the suggestion.
I'am avoiding aggregation till now because I need to keep a certain level of granularity.
@jmvidal The BI Accountant has this approach that is along the same lines: https://www.thebiccountant.com/2017/01/11/incremental-load-in-powerbi-using-dax-union/
Thank you @Anonymous !
After reading the article looks like it is not a common way to deal with large data series when you just need to update recent info.
I thought it would be a more popular request...
@jmvidal I am doing this with transaction data: 2015 to 2019 data is static and then 2020 data is refreshed. Then I use the UNION command. It makes the data refresh much faster.
Thanks, that makes sense. That's definitely what I'm going to try.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
112 | |
97 | |
85 | |
67 | |
59 |
User | Count |
---|---|
150 | |
120 | |
99 | |
87 | |
68 |