Unexpected index scan instead of seek on update

by Luke   Last Updated May 28, 2018 10:06 AM

We have a third party application which is performing badly. An update statement is performing a scan instead of a seek, and is not suggesting a missing index. Why is this happening?

I was expecting the execution plan to suggest a missing index like

create nonclustered index [ix_FluxInbox_tasklockedby] on Flux.dbo.FluxInbox (tasklockedby) include (tasklockedrole, tasklockedon)

Below is the execution plan enter image description here

The details of the index scan

enter image description here

Related Questions

Index Seeks cost or OR operator

Updated June 25, 2018 21:06 PM