In my Deadlock thread, was I wrong to admonish the former MVP over his first post? It just hit me wrong.

SQLRNNR (10/1/2015)

---

To recap:

1. Profiler filter issue resolved. You see the deadlocks there now.

2. No indexed views

3. Tuning the code is far from feasible currently.

4. Tracking down how the app accesses...

No jobs are active on the test server.

GilaMonster (10/1/2015)

---

Lynn Pettis (10/1/2015)

---

Only filter used was to the database and user involved (all connections use...

We...

Thanks, Gail. Trapping only the Deadlock Graph with no filters worked.

Never tried this, but can you load two different trace files into a single instance of Profiler to correlate actions captured by different traces?

Jacob Wilkins (10/1/2015)

---

The trancount for those sessions is 2, so it could be as mundane as locks hanging around from other statements in other transactions. In that case, it would...

ScottPletcher (10/1/2015)

---

Lynn Pettis (10/1/2015)

---

ScottPletcher (10/1/2015)

---

You should get rid of the INSULL() in the WHERE clause, as always. Just NEVER use ISNULL() in a WHERE or JOIN. But it's...

ScottPletcher (10/1/2015)

---

You should get rid of the INSULL() in the WHERE clause, as always. Just NEVER use ISNULL() in a WHERE or JOIN. But it's esp. important if...

Only filter used was to the database and user involved (all connections use the same user)....

Note, the indexes involved in the deadlock are both nonclustered indexes. There are no foreign key references between the tables OperationsSIGACTDraftReport or Workflow.

The queries are embedded SQL in the...

Anyone have any idea why Profiler wouldn't capture the deadlock graph even when it was the only thing being captured?

Attached is just one of the deadlock graphs in a zip file.

Okay, I found that it is the index key has value. What does that mean?