Have you looked at the execution plan? I'd say it's probably the LIKE statement. However, you need to determine how SQL Server is resolving your query and that answer is...

I have a standing offer on LinkedIn to promote anyone looking for work. I'll double down on that for Threadizens. I can actually say I know that you know what...

I'm not sure I understand the question. Yes, the SPID above should match any SPID you capture using Profiler or Extended Events.

But...

The biggest issue...

READUNCOMMITTED and NOLOCK cannot be specified for tables modified by insert, update, or delete operations. The SQL Server query optimizer ignores the READUNCOMMITTED and NOLOCK hints in...

And another. Cleaning up tabs.

One more

Klaus Aschenbrenner

Brent Ozar

READUNCOMMITTED and NOLOCK cannot be specified for tables modified by insert, update, or delete operations. The SQL Server query optimizer ignores the READUNCOMMITTED and NOLOCK...

Are they part of larger batches? There could be multiple statements involved.

Adding NOLOCK here, or almost anywhere, is a bad idea.

Look, if you really want to have dirty reads, change your connection string to use READ_UNCOMMITTED. That's the same as NOLOCK,...

You've identified some queries, but now you need to investigate their behavior within the system. The way to do this is to look at the execution plan in order to...

Thank you for those posts Grant. It helps to try and reset your view when there's so much going on that can drain us emotionally right now. I'm not...

GOOD MORNING GRANT!!!!

I recently saw an article about "Self-made men" and it expresses exactly the way I feel.  To summarize, I'm definitely not "self-made".  I'm where I'm at because...

Very kind words. Thanks.

Yeah, the curse and blessing of capturing the queries is you get to see exactly what's going on. Little things like that 19,700 executions accumulate in an insane manner to...