Can you post the plans? Hard to say anything generic for this kind of thing.

You'd be mostly looking for how the data movements changed, since those are usually the slowest...

It's parameter sniffing, or more specifically it's lack of parameter sniffing.

SQL can't tell the value of variables at compile time, and so it will assume a certain row count based...

You can use a SET statement to set deadlock priority to high, or you can tune code so that it runs faster and doesn't deadlock.

It's not about how long it...

"I have no idea. I asked online for someone to give me an...

WayneS (3/31/2016)

---

BL0B_EATER (3/31/2016)

---

Brandie Tarvin (3/31/2016)

---

GilaMonster (3/31/2016)

---

If it was my corruption session, then:

All severity 20 and above.

Error 825 (which is a severity 10 informational message that tells you that your IO...

No way, from the query, to determine the join algorithm used. SQL is a declarative language. You tell SQL what the results should be, it figures out how to execute...

No I'm not asking you to determine something, I'm asking you what you're trying to do and what, specifically and precisely, you're after, as your question, as it stands, cannot...

What do you mean by 'what kind of algorithm'? What are you trying to determine?

We're not asking for actual customer data. Just data that looks like it enough to write queries.

There shouldn't be any change in memory usage. The pages database pages are still the same size, encrypted on disk, decrypted in memory.

The big thing is backup compression. Since an...

If it was my corruption session, then:

All severity 20 and above.

Error 825 (which is a severity 10 informational message that tells you that your IO subsystem is failing)

Plus alerts on...

Fix the problem, not the symptoms. Deadlocks are mostly a case of poor indexing and/or inefficient queries..

https://www.simple-talk.com/sql/performance/sql-server-deadlocks-by-example/

No. Temp tables are session-scoped, you cannot access a temp table created in another session, not to...

No.

Data is being changed, therefore you may still get missing rows and duplicate rows (depends on how SQL accesses the table and where the other data modifications are and whether...

Hence the difference in restore times.

Might be worth having a chat with the VM admins and SAN admins, see if they can determine why there' such a difference.