Post reply

Resolution for SSIS Package Catastrophic Failure

  • July 16, 2015 at 12:03 am

    #319788

    Comments posted to this topic are about the item Resolution for SSIS Package Catastrophic Failure

  • July 16, 2015 at 3:39 am

    #1812880

    Interesting, thanks for posting this: I'm sure that it will help others.

    The absence of evidence is not evidence of absence
    - Martin Rees
    The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
    - Phil Parkin

  • July 16, 2015 at 9:48 pm

    #1813163

    Thank you so much for this. I had this issue developing over time. I could mitigate it by falling back on older versions.

    I know I have a legacy server where a couple packages are in this state, I was just hoping I would never have to change nothing to these packages since they are legacy.

    Your solution is a real life saver.

    In my case I guess the problem was somewhat caused by using a third party monitoring and notification application and somehow sometimes, the code got lost in the continuum.

    Very rarely but still when it happens, you end-up with a package you cannot trust anymore and it is always a package you really do not want to rewrite from scratch.

    Thank you.

    BI Guy

  • July 29, 2015 at 10:06 am

    #1815790

    Glad that I was able to help developer community.

    Thanks

  • July 29, 2015 at 10:07 am

    #1815791

    Thanks.

Viewing 5 posts - 1 through 4 (of 4 total)

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