I have a DTS package and a config file. I want to use DTUtil tool to install the package in the msdb database of a SQL Server instance. Now when I read the following URL http://msdn.microsoft.com/en-us/library/ms162820.aspx I don't find anything for specifying the location of the config file in the target server. Can you let me know how can I tell the ssis to pick the config file from a particular location when the package has been isntalled in MSDB?

Hi, It's depends the way what you want execute it... if is with DTExec, the config file must be an argument. If is with SQL Agent, you can set it on step configuration, under Configurations section. See http://msdn.microsoft.com/en-us/library/ms162810.aspx for DTExec parameters Víctor M. Sánchez García (ES) (BI) Hope this help. Please vote if you find this posting was helpful. if this is an answer to your question, please mark it. http://bifase.blogspot.com | http://twitter.com/atharky

The path to Config File has to be declared in the Package itself. If you are able to use Environ variable, you can use one to store the path to your Config File and use indirect Configuration in your package.

Define a Environment variable in Development and target server to store the location of config file and use the same Environment variable in SSIS indirect configuration by choosing option Configuration location is stored in an environment variable . see the steps here http://msdn.microsoft.com/en-us/library/ms365339.aspx Cheers, Shailesh

Here is a question. When I create a deployment package using BIDS and I install the ssis package using the wizard, it does ask for a location of config file and then the config file is always picked up from that location even when I don't specify it on the command line parameter of dtexec. So what does the install wizard do? does it alter the package and changes the path? or does it setup and environment variable? or any other thing?

Here is a question. When I create a deployment package using BIDS and I install the ssis package using the wizard, it does ask for a location of config file and then the config file is always picked up from that location even when I don't specify it on the command line parameter of dtexec. So what does the install wizard do? does it alter the package and changes the path? or does it setup and environment variable? or any other thing? It seems to me that the wizard creates a package configuration that points to your config file. You can check by exporting the file from the server to your filesystem and open that package in BIDS to see what has changed. MCTS, MCITP - Please mark posts as answered where appropriate.

That's the question. It should do but I can't confirm that. In my tests the path to Config File was not changed in my packages. So I prefer the same folder structure in Dev as in Prod if I have nor permissions to use an Evironment variable.

So I prefer the same folder structure in Dev as in Prod if I have nor permissions to use an Evironment variable. That is usually the way to go. Or use SQL Server configurations. :)MCTS, MCITP - Please mark posts as answered where appropriate.

> So I prefer the same folder structure in Dev as in Prod if I have nor permissions to use an Evironment variab Very honestly I don't trust environment variables. also I don't want same structure as dev because in my case I will have to create paths in prod server like c;\rohit\temp\junk\yetanotherattempt\doesitwork\foo.txt :)

Very honestly I don't trust environment variables. also I don't want same structure as dev because in my case I will have to create paths in prod server like c;\rohit\temp\junk\yetanotherattempt\doesitwork\foo.txt You don't trust environment variables? What did they ever do to you? :) And you also don't want to use the same folder structure. That is a bit of a problem. If you want to deploy the package between environments, you don't want to change the connectionstring to the config file each time manually. Unless you want to get in trouble of course. You can also do it with a registry setting, but I guess that when you don't trust environment variables you also don't trust the registry :)MCTS, MCITP - Please mark posts as answered where appropriate.

>You can also do it with a registry setting, but I guess that when you don't trust environment variables you also don't trust the registry :) Registry settings you say? I will have to run across the room screaming in horror!!!!

See this post: SSIS: Indirect configurations ROCK! http://consultingblogs.emc.com/jamiethomson/archive/2005/11/02/2342.aspx I advocate you adopt this approachArthur My Blog

The problem is that while developing packages people should have developed it with indirect config. Otherwise an admin can do nothing.

Hi MSDN Student, I am not sure why you cannot find the config file in the target server, please take the following artiles as a reference, and hope they could help you. Configuring the Integration Services (SSIS) Service: http://msdn.microsoft.com/en-us/library/ms137789.aspx SSIS Package Configurations: http://msdn.microsoft.com/en-us/library/ms141682.aspx If you have any question, please feel free to ask. Thanks, Eileen