This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 0%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJB%3C/text%3E%3C/svg%3E)
Hi, according to the query store's tracked_query report an old plan comes back and used again by the execution engine even if that plan was neither manually nor automatically forced. James
Finally I realized this- what you also wrote. Just this "newly introduced" plan_id confused me. It would be better to use the good old plan hash (fingerprint) The same plan hash means the same plan the optimizer comes up. Thank you
Hi @Jozsef Basa
Looks like this issue is solved.
If Erland's answer is helpful to your question, please accept it as an answer so that other users with similar questions can see it more easily. :)
Not sure that I understand here. Even if the plan is not forced in any way, it is perfectly possible that the optimizer comes up with the same plan as it has done before. Can you elaborate a little more?
Finally I realized this- what you also wrote. Just this "newly introduced" plan_id confused me. It would be better to use the good old plan hash (fingerprint) The same plan hash means the same plan the optimizer comes up. Thank you
It could be that there subtle are differences between the plan. Differences you would need to compare the XML in a diff tool to detect.