Hi Alexey, Thanks. So there is no hook in Session object to retrieve the SqlCommand behind ?

There are two events where we give access to the actual DbCommand instance of the query - Session.Events.OnCommandExecuting and Session.Events.OnCommandExecuted. The first one is triggered before command starts execution and the second - when command is completed successfully or with error. But I cannot guarantee that everything will work fine if you cancel the DbCommand before OnCommandExecuted has been triggered. According to SqlCommand.Cancel() documentation, results of this operation may vary depending on several factors.