How can i minimize the deadlock for the below event

Question

<deadlock>
 <victim-list>
  <victimProcess
id="process2ccd0c8"
/>
 </victim-list>
 <process-list>
  <process
id="process2ccd0c8"
taskpriority="0"
logused="472"
waitresource="RID: 7:1:301805:0"
waittime="4729"
ownerId="218717433"
transactionname="implicit_transaction"
lasttranstarted="2015-02-18T02:01:42.190"
XDES="0x8ff01f078"
lockMode="S"
schedulerid="2"
kpid="19796"
status="suspended"
spid="161"
sbid="0"
ecid="0"
priority="0"
trancount="1"
lastbatchstarted="2015-02-18T02:01:42.197"
lastbatchcompleted="2015-02-18T02:01:42.193"
lastattention="1900-01-01T00:00:00.193"
clientapp="Microsoft SQL Server JDBC Driver"
hostname="xxxxxxxxxxxx"
hostpid="0"
loginname="xxxx"
isolationlevel="read committed (2)"
xactid="218717433"
currentdb="7"
lockTimeout="4294967295"
clientoption1="671088672"
clientoption2="128058">
   <executionStack>
    <frame
procname="adhoc"
line="1"
sqlhandle="0x02000000f96c7e18b47b33db0c837f7598795780ea68c03a0000000000000000000000000000000000000000">
SELECT LOC as LocationName, MATERIALUNITOFMEASURE,
SUM(WMDLXK.DECODE(QTY_TYPE,'QA',QTY,0)) QUANTITY_ON_HAND,
SUM(WMDLXK.DECODE(QTY_TYPE,'QP',QTY,0)) QUANTITY_ON_ORDER,
SUM(WMDLXK.DECODE(QTY_TYPE,'QS',QTY,0)) QUANTITY_SOLD,
SUM(WMDLXK.DECODE(QTY_TYPE,'--',QTY,0)) QUANTITY_ON_DEMAND,
SUM(WMDLXK.DECODE(QTY_TYPE,'QO',QTY,0)) QUANTITY_OUT_OF_STOCK,
SUM(WMDLXK.DECODE(QTY_TYPE,'QR',QTY,0)) QUANTITY_RECEIVED,
SUM(WMDLXK.DECODE(QTY_TYPE,'--',QTY,0)) QUANTITY_REQUESTED,
SUM(WMDLXK.DECODE(QTY_TYPE,'--',QTY,0)) QUANTITY_RETURNED,
SUM(WMDLXK.DECODE(QTY_TYPE,'--',QTY,0)) ADJUSTMENT_INVENTORY_QTY
FROM
SELECT DISTINCT LOC_SDQ3 AS LOC, MATERIALUNITOFMEASURE, QTY_SDQ4 AS QTY, QTY_TYPE FROM WMDLXK.CDM_LOCATION_QUANTITY T WHERE LOC_SDQ3 IS NOT NULL AND EDI_BATCH_ID ='erh7ck009edns0ia00003pi92015 02 18 02:01:41'
AND LINE_NUM ='1'
UNION
SELECT DISTINCT LOC_SDQ5 AS LOC,  MATERIALUNITOFMEASURE, QTY_SDQ6 AS QTY, QTY_TYPE FROM WMDLXK.CDM_LOCATION_QUANTITY T WHERE LOC_SDQ5 IS NOT NULL AND EDI_BATCH_ID ='erh7ck009edns0i   
</frame>
    <frame
procname="unknown"
line="1"
sqlhandle="0x0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000">
unknown   
</frame>
   </executionStack>
   <inputbuf>
SELECT LOC as LocationName, MATERIALUNITOFMEASURE,
SUM(WMDLXK.DECODE(QTY_TYPE,'QA',QTY,0)) QUANTITY_ON_HAND,
SUM(WMDLXK.DECODE(QTY_TYPE,'QP',QTY,0)) QUANTITY_ON_ORDER,
SUM(WMDLXK.DECODE(QTY_TYPE,'QS',QTY,0)) QUANTITY_SOLD,
SUM(WMDLXK.DECODE(QTY_TYPE,'--',QTY,0)) QUANTITY_ON_DEMAND,
SUM(WMDLXK.DECODE(QTY_TYPE,'QO',QTY,0)) QUANTITY_OUT_OF_STOCK,
SUM(WMDLXK.DECODE(QTY_TYPE,'QR',QTY,0)) QUANTITY_RECEIVED,
SUM(WMDLXK.DECODE(QTY_TYPE,'--',QTY,0)) QUANTITY_REQUESTED,
SUM(WMDLXK.DECODE(QTY_TYPE,'--',QTY,0)) QUANTITY_RETURNED,
SUM(WMDLXK.DECODE(QTY_TYPE,'--',QTY,0)) ADJUSTMENT_INVENTORY_QTY
FROM
SELECT DISTINCT LOC_SDQ3 AS LOC, MATERIALUNITOFMEASURE, QTY_SDQ4 AS QTY, QTY_TYPE FROM WMDLXK.CDM_LOCATION_QUANTITY T WHERE LOC_SDQ3 IS NOT NULL AND EDI_BATCH_ID ='erh7ck009edns0ia00003pi92015 02 18 02:01:41'
AND LINE_NUM ='1'
UNION
SELECT DISTINCT LOC_SDQ5 AS LOC,  MATERIALUNITOFMEASURE, QTY_SDQ6 AS QTY, QTY_TYPE FROM WMDLXK.CDM_LOCATION_QUANTITY T WHERE LOC_SDQ5 IS NOT NULL AND EDI_BATCH_ID ='erh7ck009edns0  
</inputbuf>
  </process>
  <process
id="processabf1498"
taskpriority="0"
logused="41352"
waitresource="RID: 7:1:301806:33"
waittime="4766"
ownerId="218712317"
transactionname="implicit_transaction"
lasttranstarted="2015-02-18T02:01:38.403"
XDES="0x8ff87e568"
lockMode="U"
schedulerid="9"
kpid="19044"
status="suspended"
spid="149"
sbid="0"
ecid="0"
priority="0"
trancount="2"
lastbatchstarted="2015-02-18T02:01:42.190"
lastbatchcompleted="2015-02-18T02:01:42.183"
lastattention="1900-01-01T00:00:00.183"
clientapp="Microsoft SQL Server JDBC Driver"
hostname="xxxxxxxxxxm"
hostpid="0"
loginname="XXXX"
isolationlevel="read committed (2)"
xactid="218712317"
currentdb="7"
lockTimeout="4294967295"
clientoption1="671088672"
clientoption2="128058">
   <executionStack>
    <frame
procname="adhoc"
line="1"
stmtstart="40"
sqlhandle="0x02000000f91f4423850b7703e5697b611b66f2000795329b0000000000000000000000000000000000000000">
DELETE  FROM WMDLXK.CDM_LOCATION_QUANTITY  WHERE EDI_BATCH_ID = @P0   
</frame>
    <frame
procname="unknown"
line="1"
sqlhandle="0x0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000">
unknown   
</frame>
   </executionStack>
   <inputbuf>
(@P0 nvarchar(4000))DELETE  FROM WMDLXK.CDM_LOCATION_QUANTITY  WHERE EDI_BATCH_ID = @P0          
</inputbuf>
  </process>
 </process-list>
 <resource-list>
  <ridlock
fileid="1"
pageid="301805"
dbid="7"
objectname="WMIDPEN2.WMDLXK.CDM_LOCATION_QUANTITY"
id="lock827cedd00"
mode="X"
associatedObjectId="72057594062766080">
   <owner-list>
    <owner
id="processabf1498"
mode="X" />
   </owner-list>
   <waiter-list>
    <waiter
id="process2ccd0c8"
mode="S"
requestType="wait" />
   </waiter-list>
  </ridlock>
  <ridlock
fileid="1"
pageid="301806"
dbid="7"
objectname="WMIDPEN2.WMDLXK.CDM_LOCATION_QUANTITY"
id="lock4e67a3c00"
mode="X"
associatedObjectId="72057594062766080">
   <owner-list>
    <owner
id="process2ccd0c8"
mode="X" />
   </owner-list>
   <waiter-list>
    <waiter
id="processabf1498"
mode="U"
requestType="wait" />
   </waiter-list>
  </ridlock>
 </resource-list>
</deadlock>
Please help me, How can i minimize the deadlock issue for this event

Answer 1

Indexing improvements might greatly improve query performance and reduce likelihood of deadlock, but they are no guarantee to remove deadlocks.
An additional strategy you might try is to serialise the queries. I am guessing that the SELECT and DELETE start at similar times getting IS and IX table locks respectively. Then the DELETE is escalating to a table X lock, for which it must wait for the
IS lock to go. The SELECT query continues until it needs a record/page that is X locked by the DELETE statement. That would be a deadlock. For the DELETE, you might get a full table lock at the beginning of the query. ie try changing the DELETE to the following
BEGIN TRANSACTION
SELECT TOP 0 * FROM WMDLXK.CDM_LOCATION_QUANTITY WITH (TABLOCKX)
DELETE  FROM WMDLXK.CDM_LOCATION_QUANTITY  WHERE EDI_BATCH_ID = @P0
COMMIT TRANSACTION
The SELECT in the query above will wait until it can get a full table X lock. No deadlock as it will wait for executing select queries to complete. Then the DELETE statement can execute within the full table X lock, so no deadlock there. At the COMMIT, the
full table X lock is released and waiting SELECT queries can continue.
Note: The SELECT queries will be slowed up (waiting for shared lock) while the DELETE executes. Are you OK with that? Actually, it is slightly worse, as a SELECT query might have to wait while the DELETE waits for its X lock, then wait while the DELETE executes.
Hope that helps,
Richard