take a look at this
insert into
which is not sargable , so it will cause a scan, but if no rows are found, the insert will not happen ... the scan is still happening
but if you did, the cost should drop sharply, because now you can use the index
insert into
BTW I would use STATISTICS TIME and STATISTICS IO instead of measuring performance, these two are much better indicators. When you see 3 reads versus 10,000 reads, you know what happens. What 45% tell you exactly when the whole process can run for 3 minutes or 3 seconds
SQLMenace
source share