March 26, 2016 at 11:34 am
Hi,
I have a SSIS package with FTP task. When I run I got error Login is not allowed.
So I changed the package encryption using encrypt sensitive data with password. It ran fine from command line but how it will work through SQL Job?
Do we need to change anything? The package doesn't have any configuration file
March 29, 2016 at 12:11 am
SQL server agent jobs has an option to run SSIS package as step
very straight forward, if you can google you get loads of blogs but this is the closest I can think of
https://www.mssqltips.com/sqlservertutorial/220/scheduling-ssis-packages-with-sql-server-agent/
March 29, 2016 at 10:36 am
It works me in this way
Instead of running as proxy account, you can modify the SQL job enter the password at the commandline. It is working fine for me
March 29, 2016 at 10:45 am
ramana3327 (3/29/2016)
It works me in this wayInstead of running as proxy account, you can modify the SQL job enter the password at the commandline. It is working fine for me
This may 'work fine', but it does not sound secure.
April 25, 2016 at 3:26 pm
Why it is not good option?
April 25, 2016 at 4:23 pm
ramana3327 (4/25/2016)
Why it is not good option?
Storing passwords anywhere in plain text, when there is an alternative not to, is why.
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply