any way to reduce the # of executions of the index seek on object28.index25?

michael albert 2017-09-14 14:24:46

a recent upgrade of the software has caused reduced performance -one table, object28, goes from being scanned once, with 3k logical reads, to being scanned 46 million times with 148million logical reads. this is the same code, with just version differences of IC.

the index seek on object28.index25 gets executed

the indexes on the two tables involved haven't changed that i can see.

any ideas much appreciated, i am stuck on what to try/recommend.