Challenge here is that Query is not performing bad, in fact after first execution it takes less than 1 second, which is good, but I want it to revert back to original duration and then I can plan re write, if various other optimization steps fail. I do not want it rely on various caches to start with. If after first execution I cannot get the original time, then there's little I can do to to optimize

Currently, I am attaching the execution plan after first execution where it takes less than 1 second, as per a colleague, strange part is that there's no difference in the execution plan in the either case