blocking scenario

Question

Hi All,

I am seeing a session is blocking another session which is started much later. I am saying this based on start_time and duration columns using sp_whoisactive. is it possible or its a timing issue? Can anyone explain how that's possible?

DELETE statement is blocking any UPDATE statement on a view.

Regards,

Sam

Answer 1

I'm not sure what your question is. One session is blocking another. The blocking session happened to connect later than the blocked session, what would be strange by that? I assume the two processes are running different operations. The first process visited all sorts of places, and only came to New York and the Brooklyn bridge after more than an hour. The second process went straight for the bridge and put up a roadblock.

Answer 2

Hi @Sam

Thank you for reaching out to us with your query.

Based on your description, it is possible that a session is blocking another session that started much later. Yes, it is possible for a session to block another session that started later.

This can happen due to various reasons, such as long-running transactions, lock contention, or resource contention.

This can also happen when the earlier session holds a lock on a resource that the later session needs to access. The later session will be blocked until the lock is released by the earlier session. This can cause a cascading effect, where multiple sessions are blocked, leading to performance issues and delays.

To troubleshoot such issue, as you are using sp_whoisactive to identify the blocking sessions and the resources they are blocking.

Once you have identified the blocking sessions, you can take appropriate actions to resolve the issue, such as optimizing the queries, reducing the transaction duration etc.

Let us know if you have any further questions or need additional information.

Thank you!