Hello I've been given the task of migrating a DTS package to SSIS (neither of which I am particularly familar with). The first job in the DTS package is to read a .ini file and set a bunch of variables. These variables are then used throughout the DTS package. After running the DTS package through the SSIS migration wizard this job turns into an execute script task and I can't see if it is still reading the .ini file. However, the only real purpose of this step is to allow different parameters to be passed in development, test, production etc. So I am thinking this whole step can be removed and effectively replaced with a package configuration (I'll probably use an XML file). My understanding is that by selecting the name/value pairs as appropriate in the XML package configuration file means this values will be passed in at runtime and achieve the same functionality. Is this the correct way to do this in SSIS, or do I still need the .ini file and variables? Thanks for any advice on this issue. Regards, John

Yes; package configurations are the preferred way to solve this problem in SSIS. Just configure the variables, and create three copies of the dtsConfig file, one each for dev, test and prod. There are lots of ways to do this, but configurations are generally the simplest. Check out this post for information on indirect package configurations too: http://blogs.conchango.com/jamiethomson/archive/2005/11/02/SSIS_3A00_-Indirect-configurations-ROCK_2100_.aspx

Hi Matthew Thanks for this, thought I was on the right track. Just one point of clarification however - do I actually need the Variables in order to use the package configuration? As an example the old DTS ini file reads in the location of a source data file and stores this in a variable. But my impression is that in SSIS I could enter this path directly into my development SSIS package, save this attribute as part of the configuration file, and then change its value in test and production at run time just by changing the package configuration file entry - no variable needed. Is this right? Thanks, John

You can do it either way, but I strongly prefer to only configure variables and then to use package configurations to get the values from the variables to where they need to be used. This provides more opportunities for reuse and makes the packages more resistant to change, but either approach will deliver the functionality you require.

Hi friends, package configurations are ok in the most of cases. but in my case the parameters should be given by users (company id, budget id, year id,...), who do not have the obligation to understand xml files. In SQL2000 I used ini files, which were easy to handle for users. How can I offer the user an easy way to provide parameters for the execution of the package?

You can use SQL Server Configuration instead of XML-File. Create a small application for the Users to change the values of the parameter.

Is it me, or does it really sound weird that users have control over the ETL process? What are the requirements, if I may ask?MCTS, MCITP - Please mark posts as answered where appropriate.

The users can choose the company and period before trigger the process.