Hi All
Looks like this issue is coming up in SQL server DB when there are many concurrent process trying to update access the same table at the same time. In my case there were 200 concurrent process which where completing almost the same time.
Looks like when there are too many updates in SQL server DB row locks are converted to table level locks resulting in this behavior. One solution is using some connection pooling solution which allows default isolation level as snapshot isolation level in SQL server. Unfortunately I could not find any open source connection pooling API using which I could achieve the same.
Thank you
Krishnendu