Very handy when you have lots of connections.
I’ve been meaning to post this one, so finally got to it…In order to troubleshoot design-time validation issues, a nice feature of BIDS is the Properties>>Execution>>DelayValidation property of SSIS. This is really great when you have sources or destinations that you either can’t connect to at the moment, or have many connections that must be changed when moving the package from development to production; although SSIS configurations are handy, they sometimes don’t get everything wired back up, and right clicking and editing the package on the new server is required. DelayValidation can be set at the Control Flow level, the container level, or at the ‘top’ data flow level.
In my case, I didn’t want SSIS to ping all of the connections in my package, because mine had several SAP 1.0 tasks, and all had to be reconfigured during such a move for the production environment. This was especially convenient since the number of failed attempts for SAP defaults to eight and cannot be changed. (Or so I’m told by the SAP expert). When the .dtsx file was moved, SSIS attempted to verify those connections and subsequently exhausted all of the login attempts, one for each SAP task. Talk about a beat down.
More reading on MSDN
Lee
------------------------------
I see where my title at work is now ‘Manager’. Hope they tell me what I’m managing.
05e13c90-49d3-41f2-803c-4652b7a5bbe0|0|.0