trigger AFTER SERVERERROR ON DATABASE

In our instalation, we control maximum IO or CPU call usage using profiles. We are using "after servererror" event to capture problematic statements.

But if triggering event is in between a stored procedure, the trigger returns the procedure call and not the triggering statement.

Is there any way to catch the effective statement but not the stored procedure where it is contained?

Thanks,

Carlos Julio Peixoto