Why isn't my SSIS configuration update being saved?
I have an SSIS 2005 package that is up and running in our production environment. The package uses the SMTP Connection Manager to send an email message to a designated user. We have a scheduled job that runs this package and also cancels the SMTP connection string so that the package can target a test or production mail server, allowing us to maintain a single service across our test and production servers just configured differently.
We recently changed the server name of our production mail server and went to a scheduled job and changed the command line values that are run to point to the new server. However, the next morning the job failed and the error log indicates that the job tried to connect to the old mail server.
Is there something I am missing to update SSIS package parameters? Do I have to remove the existing package and then reimport and migrate the job again so that the new server change is held?
a source to share
The dba I am working with had a similar problem. They had to change the working parameters, but it seems that working with the changed parameters only worked on the first run. After that, he continued to use the old values in subsequent runs. They had to repackage the damn thing.
a source to share
Should you use the package configuration feature? It can be legible in the order of execution. There is more information there: http://msdn.microsoft.com/en-us/library/ms141132.aspx
a source to share