Post reply

SSIS package connecting to multiple remote servers

  • April 16, 2014 at 2:37 am

    #284664

    Hi All,

    I have a central SSIS package that connects to ~360 remote servers to pull back some data. The list of remote servers are built by querying a central table, passed to a foreachloop where I build a connection string in a script task then execute some SQL.

    This all works fine until there is a server unavailable where the package then fails with a SQL time out error.

    Is there a way I can trap this error and log it to allow the package to continue with the rest of the server list?

    Cheers,

    Chris

    [font="Times New Roman"]There's no kill switch on awesome![/font]

  • April 16, 2014 at 4:09 am

    #1706383

    Check out this article, Control Flow Task Errors – Level 9 of the Stairway to Integration Services[/url]

    😎

  • April 16, 2014 at 4:26 am

    #1706388

    Eirikur Eiriksson (4/16/2014)

    Check out this article, Control Flow Task Errors – Level 9 of the Stairway to Integration Services[/url]

    😎

    That article talks about handling errors using Event Handlers. What it doesn't mention is that you can stop errors bubbling up by setting the value of the Propagate variable. This article[/url] talks about how to do that.

    John

  • April 16, 2014 at 5:06 am

    #1706397

    Thanks for the response!

    I actually solved the problem with the following blog post:

    http://consultingblogs.emc.com/jamiethomson/archive/2005/10/10/SSIS-Nugget_3A00_-Verify-a-data-source-before-using-it.aspx

    I'll defo have a read through those stairways - some good moves in there !

    [font="Times New Roman"]There's no kill switch on awesome![/font]

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

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