I've got a job running which executes a stored procedure. This stored procedure then executes 23 other procedures, which in turn, execute 5 stored procedures. This may seem daft, but there is a reason for it, honest
Its mainly to keep things tidy.
When the job runs however, it seems to always fail after executing so many stored procs. I've tried moving them around to ensure that its not errors within the sprocs that are causing them to fail, but then it just fails on another, but successfully executes the ones that it was failing on previously.
Is there a limit to the number of sprocs that a job can execute? Although it always seems to fail after 19-20 minutes, I don't think its a timeout issue as we've set the server timeout to 0 (infinity).
Does anyone have any idea what might be causing this to fail? There are "divide by zero" errors coming up, but I've put "SET ArithAbort Off" in all the procedures, and in most cases it skips the errors.
Any help would be appreciated, and might help prevent me throwing myself out of the window.
When the job runs however, it seems to always fail after executing so many stored procs. I've tried moving them around to ensure that its not errors within the sprocs that are causing them to fail, but then it just fails on another, but successfully executes the ones that it was failing on previously.
Is there a limit to the number of sprocs that a job can execute? Although it always seems to fail after 19-20 minutes, I don't think its a timeout issue as we've set the server timeout to 0 (infinity).
Does anyone have any idea what might be causing this to fail? There are "divide by zero" errors coming up, but I've put "SET ArithAbort Off" in all the procedures, and in most cases it skips the errors.
Any help would be appreciated, and might help prevent me throwing myself out of the window.