I have a SQL Server 2005 database with a job which contains several steps. Each of these steps completes without issue but the overall job fails. I believe this has to do with a NULL value generating a warning so I set SET ANSI_WARNINGS OFF;
on the step I thought was generating the warning but the job still fails as a whole.
How can I either get the job as a whole to ignore warnings OR determine what is the root cause of this issue. I don't see anything in the error logs.
View Complete Post