title: Deploying SSIS Package and retaining a connection password
body: <p>I have an SSIS package that queries a view for some records then sends off an email using Database mail. I want to deploy the package to the SQL Server that these views exist in and then schedule us using SQL Server Agent but i've run into a number of issues. </p>
  
  <p>The main problem is that within the job there is a connection manager that has stored credentials for a SQL Server account that has access to the views and email profile. I've set the package to EncryptSensitiveWithPassword instead of User Key but i can't seem to find any way to actually pass that password the the SQL Server Agent when the job is run. So when it executes it fails since it can't connect. </p>
  
  <p>A bunch of websites say to use the config file, but when I go that route it breaks the job entirely complaining that the OLEDB connection can't be established. In that scenario I can't even run the job on my machine locally. </p>
  
  <p>A few other sites recommended copying the package to the local ssis package store on the machine, but I only have access to the machine through SQL Server Tools, I can't remote in or install anything on the file system so I have to install through the manifest file using the SSIS deployment process. </p>
  
  <p>I've read something about storing settings in another DB table, but that again presents issues with permissions on the server. </p>
  
  <p>Finally I tried passing /password  or /decrypt  in the job scheduler, but when i click ok it scheduler removes that parameter. </p>
  
  <p>This is an internal server and security isnt really a big concern, Any idea how i can pass the decryption password in plaintext or just tell SSIS to not bother securing sensitive data? </p>