RAISERROR Serverity 16 Showing in SQL Agent Log

Question

Viewing 4 posts - 16 through 18 (of 18 total)

You must be logged in to reply to this topic. Login to reply

Anja SSC Enthusiast Points: 166 More actions · Answer 1

Hi Hyperlance,

I had the same issue.

I also discovered a change in behaviour after moving to SQL 2022.

Our jobs have multiple steps, and I don't want to modify all of those.

Luckily the change is simple:

Replace the 'raiserror'-part by 'throw', just like this:

IF sys.fn_hadr_is_primary_replica('<dbname>') <> 1

THROW 50000, 'This is not the primary replica.', 1;

Add this line of script in the first step of the job and set that to 'fail the job showing success'.

Good luck!