Checkpoints is the foundation for restarting packages in SSIS, and they work by writing state information to a? Le after Each task completes. This le can then is used to determine which tasks has run and which have failed.
To ensure this checkpoint? Le is created correctly, your must set 3 package properties and one task property:
Checkpointfilename:this is the? Lename of the checkpoint? Le
Checkpointusage:3 Options
- Never:the package won't use a checkpoint? Le and therefore would never restart.
- If exists:if a checkpoint? Le exists in the speci? Ed for the CheckpointFileName property, then it'll be used, and the package would restart according to the checkpoints WR Itten.
- Always:the package would always use a checkpoint? Le to restart; If one does not exist, the package would fail
Savecheckpoints:this is a, simple, Boolean to indicate, whether checkpoints is, is written.
The one property has to set on the task is failpackageonfailure. This must is set for each task or container, want to is the point for a checkpoint and restart. If you don't set the This property to true and the task fails, no? Le'll is written, and the next time you invoke the package, it'll start from the beginning again.
Checkpoints occur only at the Control Flow
If you want a checkpoint? Le to is written, then make sure, and the restart Point have failpackageonfailure set to true.
SSIS->> Package restartability fullfilled by checkoints