Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
rwgraham
Starting Member
1 Post |
Posted - 2009-09-12 : 21:46:25
|
First time poster.Sorry if this is a stupid question. I am a newbie to SSIS, and do not have a box to test a deployment on yet.I want to avoid having connections spread out in config files all over the place because I have a family of apps that will run in conjunction with an SSIS app.I have a NET assembly in the GAC that manages and encrypts all the connection strings in a common xml file. This works fine for all the other apps since they are in C# and I can get everything from the GAC assembly at app start up, but not sure about SSIS and it;s validation process.Each of my SSIS package has a parent Sequence Container with a Script task that calls the GAC assembly first to get and set all the connections as the first step in the execution flow.Of course SSIS works fine in my dev environment because I also have valid defaults configured.When I deploy the packages to a new environment, if DelayValidation is set to true, will this strategy still work? Or will I be forced to use a standard config file for the SSIS application anyway because of validation errors in production.Any other gotchas that are obvious in the approach I am using?Thanks,Robert |
|
|
|
|