Evil Kraig F (1/6/2012)
Brandie Tarvin (1/6/2012)
To be clear: I'm not concerned with fixing the timeout issue itself. I've got that covered. What I'm concerned with is how to force a SQL Agent job step to fail if it runs into a timeout issue.I believe you'll have to wrap the call with a TRY/CATCH and do a custom RAISEERROR if it occurs, but I don't have the ability to modify my network to create a mini-lab to confirm I can see the same functionality and that it'll cure it.
Craig, I get what you're saying, but I can't figure out how to pass the error outside of the code context to fail the job step itself. Raising an error is, in and of itself, a successful prosecution of the code. And I see no options within the job step window that allow me to set success or failure of that job step.
The only option I'm seeing is having that error attempt to update the sysjobsteps table, but I hate the idea of updating sys tables (if I could even do that anymore).
jnuqui (1/8/2012)
FYI that SQL server checks your script before you could create the job. 😀 it should also fail during job creation.
SQL Server only checks for syntax errors and object existence during job creation. There's no reason why job creation would fail in this instance.
jnuqui (1/8/2012)
you may want to share your script for this. so we could discuss this weird event. 🙂
Exec MyServer.MyDB.MySchema.MyProc;
That's all it is, one simple line of code in a Transact-SQL job step. And I'm not the only person who has this issue. When I googled the problem, I found articles referencing SQL 2005 too with similar comments (the job step succeeded when the query timed out). Unfortunately, none of those articles had a solution to my problem.