In multithreaded application where update and select can go simultaneously assuming update is used within transaction. If table has non clustered index and clustered index, what are the chances of having deadlock in such situation? clustered index is used by update statement for example Cluster Index Update <- Clustered index seek whereas non clustered index used by select statement for example select <- nonclustered index seek What happens when one thread updates and other is using select assuming same rowids referred(where clause returns same rows)? Are there any chances of having deadlock? how such situations can be handled if application allows update and select to run concurrently?
What are the chances of occurring index row level locking deadlock?