January 15, 2013 at 3:15 am
How can I store the username and password not in the config file or SQL Server in SSIS, so that no one can identify these secured details.
January 15, 2013 at 4:26 am
The secure/best method is to not save the password in config file and use Windows Authorization. If that's not possible, save in the config and restric access to that folder.
Details: http://consultingblogs.emc.com/jamiethomson/archive/2007/04/26/SSIS_3A00_-Storing-passwords.aspx
Sam Vanga
http://SamuelVanga.com
January 15, 2013 at 4:34 am
Thanks mate..its very useful info.
January 15, 2013 at 4:35 am
January 15, 2013 at 5:08 am
You can store package configurations in the database too
Jayanth Kurup
Do you mean having a table that contains the complete connection string (i.e. including user name and password)?
---------------------------------------------------------
It takes a minimal capacity for rational thought to see that the corporate 'free press' is a structurally irrational and biased, and extremely violent, system of elite propaganda.
David Edwards - Media lens[/url]
Society has varying and conflicting interests; what is called objectivity is the disguise of one of these interests - that of neutrality. But neutrality is a fiction in an unneutral world. There are victims, there are executioners, and there are bystanders... and the 'objectivity' of the bystander calls for inaction while other heads fall.
Howard Zinn
January 15, 2013 at 5:31 am
yes , please look at the below link for details.
February 12, 2013 at 1:13 am
Connection passwords in a package can stored in package itself. SSIS provides encrypt sensitive information option in the package properties list. Best is encrypt with a password wherein you provide another password to encrypt the actual password.
April 30, 2013 at 11:10 am
When you want to schedule the job, do you need to provide the package password in the agent configuration? If so would you need to restrict access to who can view the agent ? If so that may not go far enough if there are many users with elevated priviledges.
----------------------------------------------------
May 1, 2013 at 3:43 pm
mmartin1 (4/30/2013)
When you want to schedule the job, do you need to provide the package password in the agent configuration? If so would you need to restrict access to who can view the agent ?
If the package is encrypted, you can pass in the package encryption password via the dtexec /DE switch (in SQL Agent, or most any other scheduling utility).
mmartin1 (4/30/2013)
... may not go far enough if there are many users with elevated priviledges.
Potentially a privledged permissions problem. 😀
May 1, 2013 at 10:29 pm
Seriously - go with Sam's suggestion of windows authentication and forget about all these convoluted solutions requiring special passwords to be hard coded all over the place. You have an enterprise security store - use it.
Say NO to proliferation of passwords.
May 2, 2013 at 11:02 am
Say NO to proliferation of passwords
+1
----------------------------------------------------
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply