Forum Discussion
Refresh starts over
Hi Anonymous ,
Firstly, +2 for the tidy, well-explained request and the gif. Really easy to help when people take the time to ask their question carefully and give clear information.
I think Anonymous has given you a smart solution that you should go with, but I just wanted to cover your implicit question about why your refresh appears to restart:
It's not actually restarting as such, but performing data loads for two different parts of your query. This happens with merges because there's the initial load of the table, then there's the load of it as it's merged with a second table. Even though the 'double-load' appears to be occurring on the same table (and in some respects it is) there's a second table to consider within the query, so you need to re-run the load for every row in the tableto match to your second table.
Anonymous knows some really cool tricks to speed up merges so I'd definitely be giving what he suggests a go. Myself, I tend to avoid merges like the plague for exactly the reasons above.
Pete
BA_Pete is definitely correct, ralationships in a data model definitely beats joins/merges.