Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SQL Server Administration (2005)
 How to pass SSIS password to SQL job

Author  Topic 

qman
Constraint Violating Yak Guru

442 Posts

Posted - 2010-12-17 : 13:43:15
I have a SQL Job that contains a passwordencrypted SSIS package.
How do I pass this password to the SQL Job so that the job does not fail?

Can it be added to the command line section of the job?

Thanks

webfred
Master Smack Fu Yak Hacker

8781 Posts

Posted - 2010-12-17 : 13:51:53
If I remember right then you have to give the password when making the job step and while choosing the package.
And yes there is a command line parameter for the dtexec:
http://msdn.microsoft.com/en-us/library/ms162810.aspx



No, you're never too old to Yak'n'Roll if you're too young to die.
Go to Top of Page

qman
Constraint Violating Yak Guru

442 Posts

Posted - 2010-12-17 : 13:57:46
Is this something that is set within the configuration of the job, or externally via command line?
If externally, is this something that is done once and that's it?
Go to Top of Page

webfred
Master Smack Fu Yak Hacker

8781 Posts

Posted - 2010-12-17 : 14:06:01
Just try to generate your job step and see what happens when you choose the needed package.


No, you're never too old to Yak'n'Roll if you're too young to die.
Go to Top of Page

qman
Constraint Violating Yak Guru

442 Posts

Posted - 2010-12-17 : 14:17:06
If I run the SSIS package directly from within SQL, it prompts for a password and succeeds if I provide.
If I run from a SQL job, it fails yet the Command Line within the SQL Job reads:

/SQL "\Daily_Data" /SERVER bill /DECRYPT abcd /MAXCONCURRENT " -1 " /CHECKPOINTING OFF

I guess I am mystified why it fails... I can see that decrypt is set with the proper password.
Go to Top of Page

qman
Constraint Violating Yak Guru

442 Posts

Posted - 2010-12-17 : 14:25:23
Working fine, restarting SQL Agent did the trick.
Go to Top of Page
   

- Advertisement -