Hi all,I just wanted to bump this once more, because I also believe that this feature is basically mandatory when doing any kind of performance tuning where blocks between different processes are involved.Without it, it is extremely cumbersome to identify the process that holds a lock on a ressource and makes analyzing it a huge timesink.I also wanted to mention that via Application insights, this feature is.. kind of there still? You can get the Callstack of the blocking process, but only if the process that runs into the lock timeout is on the same service tier as the blocking process.In an environment with multiple service tiers this is useless, as we do not know the process that holds the lock, and the sql tracing allowed us to quickly identify the process by simply turning it on and activate the "Debugger.EnableSqlTrace" for all sessions.Best regards,Stefan