Scribd
Upload
55 views

For Example:: Check Points

Checkpoints allow packages to restart from the point of failure rather than restarting the entire package. This document outlines how to set up checkpoints in SQL Server Integration Services packages by: 1. Configuring the package properties for checkpoint usage and saving. 2. Setting the "FailPackageOnFailure" property to true for each task to checkpoint. 3. Restarting the package from the checkpoint if a failure occurs after the checkpointed task completes successfully.

Uploaded by

Sangameshpatil
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
55 views

For Example:: Check Points

Checkpoints allow packages to restart from the point of failure rather than restarting the entire package. This document outlines how to set up checkpoints in SQL Server Integration Services packages by: 1. Configuring the package properties for checkpoint usage and saving. 2. Setting the "FailPackageOnFailure" property to true for each task to checkpoint. 3. Restarting the package from the checkpoint if a failure occurs after the checkpointed task completes successfully.

Uploaded by

Sangameshpatil
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 5

Check Points

Checkpoints are added into your control flow to ensure that if your package fails
after multiple tasks have succeeded, the progress you have made will not be
lost. We can set check points at task level not at package level.
For example:
Take two execute sql task connect them, rename it as task 1 and task 2
Double click on task1.

Like this do same thing to task 2

Right click on control flow properties


Now in order to implement this we are first going to have to change three setting
in our package properties window.
1.
The CheckPointFileName has to be populated. There are no naming
conventions required here, so name it what you like.
2.
The Second property is the CheckpointUsage property; change this to
IfExists this will allow the package to restart from a checkpoint if that
checkpoint file was created.
3.
The SaveCheckpoints property should be set to true. This simply says
that if there is a failure a checkpoint file will be saved.

Checkpoint usage properties:


1.

Never Do not use checkpoints

2.

Always Always use checkpoints, if the file does not exists package will fail

3.

IfExists Package use checkpoint file if exists otherwise it creates it

After this, right click on task1 properties


Now that your package properties are set, for each task that you wish to make a check point you have
to navigate to that tasks properties menu and switch the FailPackageOnFailure property to
TRUE. By implementing this methodology you are decreasing your chances of unnecessarily
reprocessing a task.

Do same to task 2
Execute package , and check in SSMS tables created.

Drop table ONE and execute the package at this time task 1 will execute, task 2
will fail

Xml will create

In xml

It will give message for error.


Now drop task1, execute package and check.

You might also like