x

CheckpointUsage 'Always' in SSIS

For several years checkpoints have been available in SSIS as a means of managing data consistency and restartability of a package.

One of the options to configure checkpoints is to set the package's CheckpointUsage property to always. However, I've never seen a case for using this option.

Does anyone know an application for this option, whether in theory or (even better) in practice?

more ▼

asked Apr 19, 2013 at 07:45 AM in Default

avatar image

vstrien
21 1 1 3

(comments are locked)
10|1200 characters needed characters left

1 answer: sort voted first

I am unaware of a use case for Checkpoints: Always. When I have used checkpoints in the past, I've used IfExists.

I discourage SSIS developers from using checkpoints and package restartability. I haven't looked at checkpoints in a while, but my old reasons for not using them were: 1. Checkpoints do not remember variable state. This is particularly worrisome when using Loop Containers. 2. Checkpoints stop recording successful executable completion once an error is detected. Long-running concurrent executables may be unnecessarily restarted on the next execution. This could cause duplication of effort and, perhaps, data.

Instead, I recommend writing small, decoupled SSIS packages whenever possible and executing them via an SSIS framework.

more ▼

answered Apr 22, 2013 at 02:57 PM

avatar image

Andy Leonard
332 2 2

(comments are locked)
10|1200 characters needed characters left
Your answer
toggle preview:

Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

SQL Server Central

Need long-form SQL discussion? SQLserverCentral.com is the place.

Topics:

x1199
x8

asked: Apr 19, 2013 at 07:45 AM

Seen: 1029 times

Last Updated: Apr 22, 2013 at 02:57 PM

Copyright 2017 Redgate Software. Privacy Policy