password lost

Hello,

I import a package into Integration Services (it containt 3 ole db connections to SQL Server), then I schedule this into a job.

When I run the job, it failed !

For the connections, I use a sql user and, in the step that run package, I notice that the password isn't store

I add password in the connection string ("Password=password;") and when I rerun the job, it terminate with success.

My question is: Is it possible to store the password directly into the package and so avoid password encoding several times ?

Regards

Arnaud

Arnaud H wrote:

Hello,

I import a package into Integration Services (it containt 3 ole db connections to SQL Server), then I schedule this into a job.

When I run the job, it failed !

For the connections, I use a sql user and, in the step that run package, I notice that the password isn't store

I add password in the connection string ("Password=password;") and when I rerun the job, it terminate with success.

My question is: Is it possible to store the password directly into the package and so avoid password encoding several times ?

Regards

Arnaud

Sorry, I forgot saying you that the package come from a DTS package. It has been build with the DTS migration tool.

Regards

Arnaud