I am trying to use the Checkpoint features of IS within a large
package. This package runs within a SQL job. To be production-ready,
we want to be able to restart any package by just restarting the job
step that failed. The package would then start at the correct task
based on the Checkpoint taken.

The issue I'm seeing is that there seems to be no way to always rerun a
task on restart. In this case, I have a task that puts a recordset
into a variable as an Object. Subsequent ForEach containers use the
rows in that object to drive their iteration. That means that the
setup task must always run, just in case there are ForEach containers
to be run as part of the restart.

Has anyone seen this behavior? Short of doing a redesign, have any
workarounds been discovered?

Thanks
Randy

Randy,
I have asked this question on the SSIS forum until I am blue in the face but
no-one ever answers. Unfortunately I don't think there is a way of ensuring a
task executes regardless of whether the package is started from a checkpoint
or not.
Disappointing, I know!

-Jamie

"Randy Martin" wrote: