SSIS Packages & SSSMS Jobs Security

[Ringers]

Hi All,

On my local XP machine logged on with non admin windows account. I have created an whole bunch dtsx packages in BIDS 2005 to upload data to a FTP folder. I then created some jobs in SSMS 2005 to run these packages\jobs every morning. I found that the SQL server agent account didn't have the correct permissions to run them.

I then created a SQL proxy account linked to a credential account that stored my local windows account details and the jobs run fine.

So my question is what do I do when I move the packages to the live server. The credential should still find my windows account through AD, but what happens if my password expires\changed or my windows account is disabled(when my contract finished in a few weeks).

I have tried changing the protection level to 'dontsavesenstive' but this doesn't give the SQL server agent account access.

There's got to be a better way for long term running?

Thanks

 

[SQLBill]

Save it allowing the server to maintain security. Otherwise, one problem you should run into is that the password for the package is based upon your login and the computer it was created on. When you move the package, your login may stay the same, but the computer doesn't so the password hash won't match.

-SQLBill

The following is part of my signature block and is only intended to be informational.
Posting advice: FAQ481-4875