Forum Discussion
Append vs Append as new for performance
You first want to make sure if you are using Append as New, neither of the precedent queries are set to load. Right-click both and disable the "Enable Load" menu.
As for performance, should be no issue. The command is the same - Table.Combine, and the first argument is either the previous step (Append Query) or another query (Append as New). You should only use Append as New if you have some reason to re-use the query in the query you are starting the append from in another query for some reason. Otherwise are you are just making the Query Dependency View more complex by adding another query vs just making the existing query a few extra steps.
Community ChampionYou first want to make sure if you are using Append as New, neither of the precedent queries are set to load. Right-click both and disable the "Enable Load" menu.
As for performance, should be no issue. The command is the same - Table.Combine, and the first argument is either the previous step (Append Query) or another query (Append as New). You should only use Append as New if you have some reason to re-use the query in the query you are starting the append from in another query for some reason. Otherwise are you are just making the Query Dependency View more complex by adding another query vs just making the existing query a few extra steps.