changing connection in a dts doesn't take effect

I've changed the connection in a dts to an other database server and database.

But when running the job within the scribe console it uses the old connection settings.


In detail:

I've copied a dts job and saved it under a new name. Then I edited the job and changed the target connection. Everything looks good.

I've created a new entry in Publishers/Bridge Properties to generate a new message. Then I've created a new integration process to process this message with the new dts-job. But the job seemes to ignore the new target connections settings an uses the old one.


What I'm doing wrong?


best regards


(2) Answers