Checkpoints in SSIS

Question

Post reply

Checkpoints in SSIS

Dinesh Asanka

SSChampion

Points: 11058
More actions
January 7, 2009 at 7:28 am

#99452

Comments posted to this topic are about the item Checkpoints in SSIS

My Blog: http://dineshasanka.spaces.live.com/

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Graham Lee-348559 SSC Journeyman Points: 84 More actions · Answer 1

Hi,

I have a specific checkpoint problem.

Occasionally, the SSIS package that I have scheduled will run through successfully to completion, but will not delete the checkpoint file at the end. The checkpoint file itself will have success indicators for every step in the package. Therefore the next time the package runs, it will do nothing.

This is an intermittent problem. Have you come across this before?

Thanks,

Graham

Sean Woehrle Mr or Mrs. 500 Points: 539 More actions · Answer 2

Nice article.

I think you meant, step A will not be run in one of your last paragraphs.

The article has

Execution time will be saved..."As it does not run the failed step"

Thanks,

Sean

[font="Tahoma"]Cheers,

Sean :-D[/font]

Anipaul SSC-Insane Points: 24681 More actions · Answer 3

Anipaul

SSC-Insane

Points: 24681

January 14, 2009 at 9:11 am

#926667

Nice one...

G-451588 SSC Journeyman Points: 85 More actions · Answer 4

Thanks for such a clear, concise explanation of this topic. (BTW, I've never rated an article before, so accidentally hit 1 star instead of 5. Sorry, I didn't realize it was a one-click operation. I'll know better next time!)

vishal.gamji SSCertifiable Points: 6126 More actions · Answer 5

What would be the impact of taking snapshots on evry step? i.e. if you data warehouse\db is very large? I guess i would have to include a some logic to delete the older snapshots after every step ... right?

vishal.gamji SSCertifiable Points: 6126 More actions · Answer 6

Addition to prev post:

What would be the impact of taking snapshots on evry step? i.e. if you data warehouse\db is very large? I guess i would have to include a some logic to delete the older snapshots after every step ... right? So that, only the changes are propagated on each run of the ETL.