Is the quality of error descriptions better trapped at the ssis package level rather than at the sql agent job level?
We have ssis packages executed from sql agent jobs, but if the job fails, we get 'The job failed. The job was invoked by user xxxx The last step to run was step 1'
Instead of this, is there any value to logging the error earlier from the ssis package level by using a script in the error event handler? Do the ssis errors give a better, more detailed explanation of what might have gone wrong?
It turned out that a stored procedure was changed that the ssis package depended on, but it was not obvious from the error message. So I was wondering whether ssis error collection would have told us that, instead of having to figure it out from starting from the sql job level...iow, I thionk what happened is the package error bubbled up to the job, but the detail arising from ssis was not trapped or available from there.
thanks a lot