Our application has a job which spawns multiple threads. Each thread does insert, select and delete records on the same table. When this is tested in DEVELOPMENT environment, there is a deadlock issue. On analysis it is found that this is due to page
lock by DELETE operation.
But the strange thing is that this is not happening in UAT or PRODUCTION environment.
1. When the database performance itself (due to hardware configuration or network related issues) is slow, Can possibility of deadlocks increase?
Is there any other possible reasons that could cause this? Please share.
View Complete Post