November 7, 2011 at 9:12 am
Hi,
I've spent a long time building an SSIS 2008 package to automate a lot of database operations overnight. In testing I've used EncryptSensitiveWithUserKey as the package security. I then use "Don'tSaveSensitive", together with an unencrypted configuration file, while testing it with the SQL Server Agent. I now want to deploy the package and intend to use EncryptAllWithPassword or EncryptSensitiveWithPassword to protect the database connection properties. However, I'm not sure if the SQL Server Agent will still be able to run the packages overnight if a Password is applied. Will using those encryption options prevent the package running? Is there anything I need to do/set elsewhere in the package before I add this security level?
Any advice welcomed please.
DomCiccone
November 7, 2011 at 11:55 am
You know you could test this yourself without much problem..
With that said, when you reference a package in a SQL Agent Job if it detects that is encrypted with a password it will ask for it and store it securely so that the job can run on a schedule.
As a rule I try to NEVER use usernames and passwords for connections if I can help it. And I strongly suggest this to those I mentor. I agree that sometimes this may not be possible but even if it is more difficult I will usually do it anyway.
CEWII
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply