I am using this raiserror, which is a non fatal error " RAISERROR(50016, 18,1,@ST_GL1) " however it is stopping the SQL Schedular. I don't want it to do this. I want it just to raise the error and carry on going as it was.
Don't use a severity level of 18 if you don't want the job step to "fail". To record successful completion whilst still using RAISERROR, try a severity level of 10 or less:
RAISERROR(50016, 10,1,@ST_GL1)
Cheers, - Mark
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply