I had added a new NOT NULL column into a table which was being inserted into via a stored procedure in step 3 of the job. Since I had forgotten to update that stored procedure to include the new column within the INSERT statement, the thing bombed.
However, you are quite perceptive. I have indeed (after looking into the SP) used a BEGIN TRY .. CATCH block to catch any errors during the INSERT.
OK, do you know of a way to notify the job step that a failure has occurred so that I can have a job history that reflects any handled errors?
If not, will I need to remove the BEGIN TRY logic in order for this to happen.