Have a package (several actually) that first reads c:\apps\config\mypackage.dtsconfig. This sets the servername and catalog for my database and the main bunch of config values from an SSISConfigurations table. Let's make believe we just *have*
to use that table to hold the real config values. Well, this all worked fine until they decided to put a second "test" environment on the dev server. When a package is loaded in the test environment, it should use the test instance, etc.
But it shares the c:\apps\config folder with the other instance! So now, I have trouble (at least) bootstrapping the configs into the proper environment. This is SQL 2008, btw, which seems to be extremely important as to the order in which configs
Has anybody dealt with this?
I think I can squeeze through here as long as I only have to finagle this in dev/test, and production only has a single instance. Do you see why?
Of course the goal here is to let the package configure correctly without opening it up and changing stored values just to move between environments.
Help! and TIA,
ps - yes it would be nice if you could put a "p
View Complete Post