ETLStats: Why is ReportDbDriver followed by a Sequencer?

[JKenklies]

Dear Mr. Kim,

could you please explain in short words:

What is the advantage of using a sequencer stage as last stage in Sequence after using DSJobReportDbDriver(NoWait) like you did in SeqJobStatus for example?

Should I do that too, when adding DSJobReportDbDriver to my sequences?

[chulett]

Not Mr Kim, but I always end a Sequence job with a Sequencer as that allows the last activity to have an output / exit side trigger that can be checked by the job control and thus make it restartable.

Hope none of the words were too long.

[kduke]

Craig is correct. Just call me Kim by the way.

[ray.wurlod]

Kim by the way it is.

[kduke]

Thanks Ray.

[JKenklies]

Thank you, Ray (and Kim, by the way... :p )

I'm not sure, if I really understand that. The sequencer stage is an easy way to have an output link that does nothing. So far so good, but what would happen without the output link? I thought a job was always restartable unless it aborts, isn't it? And what do you mean with job control? Is it the sequence calling the job?

[chulett]

Yah, thanks Ray... for the lame joke.

The output link doesn't "do nothing", it allows an OK trigger from the previous stage to exist that otherwise wouldn't have one and this makes the Sequence Job restartable from that last Job Activity stage if that job aborts and you have those options set. Without the trigger, an abort in the last job would mean you could not restart the Sequence from that point.

Build a small test case, easy enough to check it out and see the behaviour yourself.

[JRodriguez]

Chulett,

Looks like the behaviour is not like that anymore, I tested it with 8.1 and the sequence restarted from the last activity

[JKenklies]

Thanks Craig, I think I got it now.