SQL Server Profiler Exception tracing - Error procedure and line number omitted

by Elaskanator   Last Updated June 18, 2018 19:06 PM

Is there a trace configuration or setting that will enable the profiler to output ERROR_PROCEDURE() and ERROR_LINE() information that is always available when writing manual error handling in CATCH blocks?

enter image description here

Doing a full trace of every statement being executed is very overwhelming on active systems (I got 45k entries trying it on my test system), and even then you have to guess where the error came from based on the preceding entries.

Related Questions

Any way to catch when xp_readerrorlog fails?

Updated September 27, 2017 14:06 PM

Explicit transaction left open after try/catch

Updated July 06, 2017 13:06 PM

Output parameter in TRY/CATCH

Updated September 08, 2017 14:06 PM