I have a SSIS 2005 package that is up and running in our production environment. The package uses an SMTP Connection Manager to send an e-mail message out to a designated user. We have a scheduled job that executes this package, and also overrides the SMTP connection string so that the package can target the test or production mail server, which makes it possible to keep a single service on both our test and production servers, just configured differently.
我有一个SSIS 2005软件包,它在我们的生产环境中启动并运行。该程序包使用SMTP连接管理器将电子邮件发送给指定用户。我们有一个执行此程序包的计划作业,并且还会覆盖SMTP连接字符串,以便程序包可以定位测试或生产邮件服务器,这样就可以在我们的测试服务器和生产服务器上保留单个服务,只是配置不同。
We recently changed the server name of our production mail server and went into the scheduled job and changed the command prompt values that run to point to the new server. However, the next morning the job failed and the error log indicated that the job tried to connect to the old mail server.
我们最近更改了生产邮件服务器的服务器名称并进入了预定作业,并更改了运行指向新服务器的命令提示符值。但是,第二天早上作业失败,错误日志表明作业尝试连接到旧邮件服务器。
Is there something I'm missing to updating the SSIS package parameters? Do I have to delete the existing package, and then reimport and reschedule the job again in order for the new server change to hold?
我是否缺少更新SSIS包参数的东西?我是否必须删除现有软件包,然后重新导入并重新安排作业,以便更新新服务器?
2 个解决方案
#1
The dba's from where I work had a similar issue. They had to change a job's running parameters, but it seems like running the job with modified parameters only worked the first time they ran it. After that run, it kept using the old values in subsequent runs. They had to repackage the damned thing.
我工作的dba也有类似的问题。他们不得不改变作业的运行参数,但似乎运行修改后的参数只能在第一次运行它时才能运行。在该运行之后,它在后续运行中继续使用旧值。他们不得不重新包装该死的东西。
#2
If you are using the package configuration feature? It can be picky on the order of execution. There's some more info here: http://msdn.microsoft.com/en-us/library/ms141132.aspx
如果您正在使用包配置功能?它可以在执行顺序上挑剔。这里有更多信息:http://msdn.microsoft.com/en-us/library/ms141132.aspx
#1
The dba's from where I work had a similar issue. They had to change a job's running parameters, but it seems like running the job with modified parameters only worked the first time they ran it. After that run, it kept using the old values in subsequent runs. They had to repackage the damned thing.
我工作的dba也有类似的问题。他们不得不改变作业的运行参数,但似乎运行修改后的参数只能在第一次运行它时才能运行。在该运行之后,它在后续运行中继续使用旧值。他们不得不重新包装该死的东西。
#2
If you are using the package configuration feature? It can be picky on the order of execution. There's some more info here: http://msdn.microsoft.com/en-us/library/ms141132.aspx
如果您正在使用包配置功能?它可以在执行顺序上挑剔。这里有更多信息:http://msdn.microsoft.com/en-us/library/ms141132.aspx