Forum Discussion
Anonymous
4 years agoNot applicable
Refresh starts over
Hi all, I have a query (or a few) that was getting progressively slower and now often fails due to timing out. I noticed in the Desktop application that the refresh of certain of the bigger q...
Anonymous
4 years agoNot applicable
Before the merge: rename your IdeaID column in the second table to Idea.2. Then replace Table.NestedJoin with Table.Join and remove the new column name parameter (in quotes before JoinKind.Outer.
This will significantly improve the performance. Essentially, we are just using Table.Join instead of Table.NestedJoin.
--Nate
- Anonymous4 years agoNot applicable
The reason is that when you expand the nested tables, you are basically running the query for each row in the table.
--Nate
- Anonymous4 years agoNot applicable
Thank you for the suggestion. I will try this solution out.
- I am unsure which table you are refering to as "the second table".
- I am guessing the fact table named "Idea Table"?
- What is the reason to rename it?
- Will this disrupt any relationships the [Idea Table] IdeaID column has?
- I am unsure which table you are refering to as "the second table".