When we look at sessions being blocked in SQL Server, the session most often causing the blocking is a Session ID (SPID). However, there are some occasions where the SPID doesn't make any sense.

Using session is fragile, it's non-scalable both on the client (meaning the user can no longer use multiple tabs to parallelize processes) and on the server (for obvious reasons), and it fools you ...