I have deployed and installed an SSIS project with a package configuration. I
installed it in the msdb database. When I execute the package in Management
Studio, I am having to tell it again where the dtsConfig configuration file
is. Otherwise it executes with the last saved values in the package, not the
values in the dtsConfig file. Yet when you create a package configuration
file in SSIS Designer, it subsequently correctly and automatically reads from
the dtsConfig file and you never have to tell it again where the dtsConfig
file is. My deployment worked fine, and it deployed my dtsConfig file and
even gave me an opportunity to change the configured values within the
Package Insallation Wizard [I set the AllowConfigurationChangesProperty to
True in the project].

Is this how it is meant to work? If so, yikes, this is quite ugly! I don't
want my users to have to specify a dtsConfig file! Can someone shed some
light on this please? [I have SP1 installed but have not yet installed the
cumulative hotfix 2153 and have read the fixes in that hotfix, and they do
not address my current problem].

Charles Kangai, MCT, MCDBA

I eventually solved this problem by using an indirect package configuration.
Instead of specifying the XML configuration file directly, I specified an
environment variable that contains the path to the XML configuration file.
When I deploy my package to another machine, I just make sure the same
environment variable has been created on that machine, but then have it point
to an XML configuration file that is pertinent to that location. It now works.

Charles Kangai, MCT, MCDBA

"Charles Kangai" wrote:

Charles.

Indirect Configurations are a fantastic tool in our armoury now. We use
them all the same.

Here's a few more details

http://msdn2.microsoft.com/en-us/library/ms141682.aspx

--


Allan Mitchell
Konesans Ltd
T +44 7966 476 572
F +44 2071 008 479
http://www.konesans.com



"Charles Kangai" <CharlesKangai (AT) discussions (DOT) microsoft.com> wrote

Alan,

I understand that by using indirect package configuration you can achieve
ease of deployment accross different environments. While it may work for a
few SSIS packages well how would you manage these indirect configurations for
many SSIS pckages? Would you create different environment variables for each
SSIS package?

I also understand that SSIS will alow you to use one env var for multiple
packages. You could change the env var value just before executing the SSIS
package.

What happens when two different packages use the same environment variable
for their configuration locations and they are also required to run at the
same time? For example, I need to run 2 SSIS packages at the same time and
they share the same Env Var for their indirect pkg config. I use SQL server
to store the config values. I need to change the Env var value to have the
right filter criteria for the individual packages.

Any feedback/comments would be highly appreciated as I'm trying to set some
standards in my company with regards to SSIS deployments.

cheers,
anupam


"Allan Mitchell" wrote: