sql server dts: Hello,

I am having a bit of trouble with SSIS Configurations.

- In BIDS, I have added a configuration file and specified the properties I
want to expose.
- When I build the project, I get the standard bin\deployment folder which
contains the package file (.dtsx), the configuration file (.dtsconfig) and
the deploymentmanifest.
- Before deploying the package, I edit the config file to have the settings
I want it to for the environment I am deploying to.
- The package deploys OK
- When I work directly on the SSIS server (64 bit), I can go into SQl Mgt
Studio, choose 'run package' and when I look in the connection manager window
all the settings are as I desire ( I havent had to add a configuration file
manually)
- When I work on a client machine, I connect to the SSIS server and choose
'run package' - the properties/connections are the same as on the server but
the values themselves are completely different.

Why is this? Why when I run the package from the client (32 bit) do the
configuration values appear to be completely different? How can I run the
package remotely and pick up the configuration values that I deployed with?
Or have I misunderstood this whole configuration function?

Please, please help!

Mgale1

[quoted text, click to view]

When you install the package from manifest file on the client machine,
your config xml file will be used by wizard where you can set (for
example connection string etc). Editing only the file has no result.

To be honest, I don't completely follow when the configuration values are
being picked up from the file and when they are just the original values in
your scenario. However I'd be interested to know if you are using indirect
configurations. If not, are you sure the configuration file is being picked
up? Perhaps the client can see the config file's path but not the package
when executed on the server?
HTH,

Hello mgale1,

Indirect Configurations are very useful. Imagine this.

during development your package looks for an XML configuration file at "Z:\MyConfig.dtsConfig"
You hand it over for deployment and the server has no Z drive. So the deployment
team either put it somewhere else or nowhere.
Your package is oblivious to this so does not find a file in the location
you specified at design time.

Now, with Indirect Configurations you tell your package to look at an Environment
Variable instead.
In that Environment variable is the location of the XML configuration file.
All your package cares about is the Environment file being there.

This way you can put the config anywhere on your environment and the package
will find it.

--

Allan Mitchell
http://wiki.sqlis.com | http://www.sqlis.com | http://www.sqldts.com |
http://www.konesans.com

[quoted text, click to view]

Thanks to Paul and Christof for their replies.

I am not sure what is meant by 'indirect configurations'.

I edit the dtsconfig file before deploying the package to the server.
When I run the package on the server it seems to run with the configuration
I deployed but when I run from a client it doesnt seem to use the deployed
configuration. The connection strings displayed are not the ones that I