Tracing Exceptions and user errors in profiler back to actual code

• thisted

  SSCrazy

  Points: 2131

  More actions

  September 27, 2012 at 8:31 am

  #268255

  I would like a way to record any time there is a user error and the SQL that generated that error. Using profiler I don't see a way to programatically correlate the exception message, the user error message, and the SQL:BatchStarting/SP:Starting text data fields.

  I hate seeing errors like 'Invalid length parameter passed to the RIGHT function.' and not being able to quickly see the actual code or SP that caused the error.

  Obviously the SPID is linked between these, but the SPID is only linked for that split second between execution and error, and then that SPID is re-used for a different process. Could I somehow trigger on the exception and grab DBCC input buffer?

  Any thoughts?

• Orlando Colamatteo

  SSC Guru

  Points: 182276

  More actions

  September 27, 2012 at 10:53 am

  #1543008

  You might be able to do it using Extended Events.

  There are no special teachers of virtue, because virtue is taught by the whole community.
  --Plato