Currently DEBUGGER.ENABLESQLTRACE method is not supported in AL Language. This method helps up to turn on /off Global SQL tracing regardless of the service tier and was a very useful tool in performance troubleshooting in a busy production environment with many concurrent users and concurrent activities in C/AL language. I am sure we will face the same challenge in AL environment as well. So please support this feature (same as in C/AL).
If there is no plan to support DEBUGGER object could you please look into adding it to something like SessionInformation.ENABLESQLTRACE with exactly the same functionality. This will help to capture and log NAV Application code, NAV user name causing blocking, causing deadlocks and the application code, NAV user victim of blocking and deadlocks. Helping us to solve the performance issues better.

Another Idea is having an option in [dbo].[$ndo$dbproperty] system table in SQL so that one can turn on/off Global SQL Tracing "Globally" so that next time a session connects it will activate/de activate Global SQL Tracing (for all sessions) based on the value in [dbo].[$ndo$dbproperty] table.