If I connect JobHead to Part to PartBin, and my table order is
1 Jobhead
2 Part
3 PartBin
Is there a performance advantage to displaying all fields from JobHead before displaying fields from PartBin?
I ask because I replaced a table with a CTE table and all the new fields came in at the bottom. I moved them up to the top of the displayed columns and the speed dropped by 80%. I’m not sure if that was just due to extra frequency grease being applied to the api call at the time or if there was some logic to this nonsense.
I received various other speeds when I tried to figure out if I was onto something, but no pop ups said what I was doing made sense, so I figured asking wouldn’t hurt.
Looks like that depending on the order, SQL servers decides on different execution plans. You can download plans from BAQ designer and compare them to understand what is changing
Do you have a quick solution for what to do if that option is grayed out? I see the option in classic but it’s grayed out, and I don’t see anywhere in kinetic that has that option (cloud - working towards go live)