Similar to the Deadlock notification (see https://experience.dynamics.com/ideas/idea/?ideaid=110468a7-c3a4-ea11-8b71-0003ff68b7e1), block process notification is also required for Dynamics 365 Business Central. This process should capture the identity (user name) of the BC user who caused the blocking and all the BC users who are waiting on blocking along with the SQL command the blocking and blocked user trying to execute and the AL code stack of the blocked and the blocking user, and the resource (such as Business central table name) which was in contention. It is very useful to have other information such as SQL SPID, Host name, Database name, Wait time, CPU Time, Command, Reads etc.. as per the SQL server’s Block Process Report to be included here. In the event of a non BC user involved in the blocking chain, their SQL user name should be used and the AL code stack information will be blank. Ideally this information should be centrally provided on the SQL server's application event as a blocking chain may span users who could be potentially connected through multiple service tiers and these service tiers could be hosted in different windows servers.

Further, can this Blocking notification be available as a telemetry for both on-premise and Saas implementations. Can you please target this change to the next realise as we are having trouble troubleshooting Blocking in Business central, in SaaS implementation in particular.