You really wouldn't want no locks at all. Rows deleted while they're still being inserted, updates affecting some of the rows they should because the rest are still being inserted,...

Short answer, you probably can't.

What's the command you ran to restore and what's the exact output?

Here you go: http://www.amazon.com/SQL-Server-Query-Performance-Tuning/dp/1430267437/

Computed columns can't be edited. There's no way to make one that you can edit to entered values.

If you want a column that starts as LASTNAME + FIRSTNAME but...

Buffer pool extensions are for the data cache, specifically clean pages, not for memory grants for query execution (which is what resource semaphore waits are for)

See if this helps, since you don't need anything from the temp_eligibility table other than the row match, there's no point in a join

UPDATE eligibility

SET primary_plan = 0

WHERE EXISTS (SELECT...

You determine whether your IO config is at fault well after looking at other, simper things. Like lack or indexes or badly written queries (most commonly the cause of slow...

Ok, but the question still stands

PageIOLatch waits by themselves are not a cause...

More likely to be user-created. SQL caches temp tables. To reduce the work needed to allocate new temp tables, when one is dropped (under some circumstances) it is cached as...

jonathanmarenus (5/22/2016)

---

I need something more efficient, so I then tried the following, but the performance was even worse:

delete <tablename> a

where exists

(

select a.field1, a.field2.........a.field30

intersect

...

Well there's the cause of your performance problem.

Start with an index on each table, columns used in the where clause...

The actual plan please, not estimated.

Though, from the plan it looks like you need a couple of useful indexes.

String conversions are slower than the date functions for date manipulation, in my testing close on...

Did you try what I suggested?

Table definitions, index definitions and execution plan please.