Finding statement causing error in stored procedure with profiler
Posted on 2005-04-15
Getting the following error in a stored procedure:
"Server: Msg 8152, Level 16, State 9, Line 1 String or binary data would be truncated. The statement has been terminated."
Problem is, it's a *huge* stored procedure and I can't pin down where the error is occuring. I've tried using profiler to find what statement in the stored procedure is causing the error, but it seems I either get too much info or not enough in the trace.
Can someone please suggest what I should be looking for and what I should be tracing to figure this out (a script for a trace template would be fantastic).