Mmm. Well the purpose of my configuration file is to import certain types of information throughout the day. In my SSIS package I have many sequence containers with dummy scripts in them leading to a data flow task to import data from a text file to a SQL table. The link from the script to the data flow is conditional though dependent on the value of a boolean variable. As some tables take a long time to import, I only do them at certain times of the day. So let's say I have ten tables (table1, table2, ..., table10) and I have a variable for each (var1, var2, ..., var10) to state whether I want to import that table in this execution, my SQL2005 SSIS version had one SQL Agent job scheduled to run at midday that ran a configuration file with var1, var2, var5, and var10 set to true (i.e. import the table), and then another SQL Agent job running at midnight using the same SSIS package with a different configuration file that contained var1-var10 set to True. This worked fine before. With this change to SSIS on SQL 2008 I don't think I can take this approach any more reading what you're saying here. Have I read your comment right there please?