Find exact point where SQL Server 2000 job fails

fbellos
35 pts.
Tags:
Microsoft SQL Server 2000
SQL Server development
SQL Server errors
I am running an SQL Server Job, that executes a stored procedure with about 900 commands (mostly insert commands). The job was working OK, but suddenly fails, due to erroneous data (error message: overflow in converting numeric data to datatype numeric!). How can I find the exact point (command) where the job fails? (SQl Server error description is not very useful).
Asked: Last updated:
Related Questions

Answer Wiki

Thanks. We'll let you know when a new response is added.

You could add some logging to the procedure, for example, inserting into a log table, or using the xp_logevent procedure.

If you are using explicit transactions, you might want to log to a table variable, and insert to an actual database table from it after rolling back your transaction.

————————————

Odds are you are adding numbers up, and that the value is larger than your numeric datatype allows for.

Discuss This Question:  

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: