I have been confronted to a performance issue with a query that started performing badly (6 sec. instead of the usual 2 sec. ) following a change request that introduces a new business requirement. Below is the new execution plan stripped to the bare minimum and where table and index names have been a little [...]![]()
