I have a SQL Server Agent Job created to execute a package. I have used XML configuration and I have specified the same in the Configurations Tab in JOB properties. Today morning I had to use a different server and database but with same user credentials. So I just went to the XML configuration file, opened with notepad and changed the datasource and initial catalogue names in all the locations using Find and replace. Then I tried to execute the job, assuming the new server's data will be taken into consideration. But instead, it was somehow taking the old configuration information with old server name. But with the same config file, I executed the package manually, and it worked as expected by taking new server name into consideration. Then I tried to change the Datasource listed in DataSources tab in the Sql server job. Then I run my job, the same thing happened. So, the config file now points to the new server with proper credentials. SSIS Package runs properly taking the latest config details and pointing to new server. But the SQL Server Agent job is not woring as it still takes the old configurations. Pls Help. Added: The changes in DataSouce got reflected only when I deployed the package and installed on the machine. if this is needed each time what is the use of configuration?

Why don't you create a new SQL Job with new configure file? May be Some thing wrong with old SQL Job does its not pointing right configure file?http://uk.linkedin.com/in/ramjaddu

I never liked using XML Config files OTHER than for pointing to an SQL Configuration Database that had all the 'real' configuration stuff in it. Each Environment has its own version of the Configuration database, and every machine (server, workstation, app server, etc) that executes SSIS Packages has an XML Config file that has that one Connection String property in it. Works like a charm. Is there an additional server involved? Can it get to the XML File?Todd C - MSCTS SQL Server 2005 - Please mark posts as answered where appropriate.