Hi,
I am working on a project that uses SSIS to load a data warehouse, and I would like to know if there is a way to prevent SSIS from checking/validating the connection objects once the solution is deployed. I have tried to google for an answer and to search through this forum but I failed to find any similar examples.
We have created a SSIS project for each individual source, and individuals packages for each table/file to be loaded. Each project has also a "full load"-package that runs a "Execute Package Task" for each of the other packages. On top of this there is an SSIS_Fullload project with a single package that executes all fullloads packages within the solution. These full load packages are organized in to work in the following manner:
- Script task that checks that all connection objects are available by looping through each connection in the Dts.Connections and trying to acquire the connection. If one of the connections fail the ConnectionsAreOk-variable is set to false.
- Depending on the status of the ConnectionsAreOk the following happens:
False:Log error and send email alert
True: Continue to perform SSIS logic within a Sequence Container.
Everything works fine when I run the solution on my computer. However, once I deploy it to a SQL server instance in my own computer SSIS tries to validate the connections and fails completely. Before even attempting to run the packages. I am using a configuration file that is accessed though an Environmental Variable. Since it is all on the same computer everything is identical. One of the connection strings is deliberately set to point to an nonexistent server to test that everything works as intended.
My question is therefore, how can I force SSIS not to validate my connections? The validation causes an error on the fullload preventing the execution of other error free fullload-packages. I tried to set theDelayValidation=True but it seems to only affect object on design time.