August 6, 2009 at 7:55 am
Hey all,
Don't really work with replication to much and wondering If what I'm thinking is right here.
Basically, we have a replication job that fails from time to time, but we aren't notified of it's failure as we rely upon job failure notifications. The reason we aren't notified of failure, is the default way a replication job is created is that if step 2 (run agent) fails, that it goes to step 3 on failure (Detect nonlogged agent shutdown.), which runs and succeeds. With that said then, if step 2 fails, which it does due to network connectivity issues, than we don't get notified.
So a couple things here.
- Does it make sense to change step 2 to quit job reporting failure if the step fails instead of moving to step 3 on failure? (sp_MSdetect_nonlogged_shutdown)
- Or is it better to simply make myself a custom step that if step 2 fails, goto a step which sends an email and then continue on with the job to run sp_MSdetect_nonlogged_shutdown?
I guess I need to better understand the purpose of sp_MSdetect_nonlogged_shutdown and If I need to use if step 2 fails.
Thanks all
August 6, 2009 at 8:28 am
I say B. always better to keep your process and add to it, IMHO
August 6, 2009 at 8:37 am
I'd agree Steve and I think I'm going to do this regardless, but for my own knowledge would like to better understand the purpose of sp_MSdetect_nonlogged_shutdown, and if it's really needed, especially in this scenario.
I just find it odd that by default the way the replication jobs are created, that when this scenario occurs, that you would never know of failure if you relied upon job notifications.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply