Thank you very much! It seems the indexing of the table resolved the issue. However, we also added RETRY as an extra measure.

Thanks,

Pingala

Thanks. We implemented the RETRY to avoid deadlock. However, I am surprised how a queued DELETE got a deadlock in the first place if SQL Server does queued operations sequentially.

As the DELETEs are queued to SQL server, I thought it will take care of on executing synchronously

I am not sure how many rows are in a particular "queued" delete operation. Does indexing help?