InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 19 Jun 2013 12:32:24 GMT20http://www.sqlservercentral.com/Forums/Topic1407124-147-1.aspx[quote]Say NO to proliferation of passwords[/quote]+1Thu, 02 May 2013 11:02:28 GMTmmartin1http://www.sqlservercentral.com/Forums/Topic1407124-147-1.aspxSeriously - 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.Wed, 01 May 2013 22:29:43 GMTnick.mcdermaidhttp://www.sqlservercentral.com/Forums/Topic1407124-147-1.aspx[quote][b]mmartin1 (4/30/2013)[/b][hr]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 ? [/quote]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).[quote][b]mmartin1 (4/30/2013)[/b][hr] ... may not go far enough if there are many users with elevated priviledges.[/quote]Potentially a privledged permissions problem. :-DWed, 01 May 2013 15:43:32 GMTdg227http://www.sqlservercentral.com/Forums/Topic1407124-147-1.aspxWhen 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.Tue, 30 Apr 2013 11:10:20 GMTmmartin1http://www.sqlservercentral.com/Forums/Topic1407124-147-1.aspxConnection 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.Tue, 12 Feb 2013 01:13:03 GMTRSumanhttp://www.sqlservercentral.com/Forums/Topic1407124-147-1.aspxyes , please look at the below link for details.[url]http://msdn.microsoft.com/en-us/library/ms141682.aspx[/url]Tue, 15 Jan 2013 05:31:51 GMTJayanth_Kuruphttp://www.sqlservercentral.com/Forums/Topic1407124-147-1.aspx[quote]You can store package configurations in the database tooJayanth Kurup[/quote]Do you mean having a table that contains the complete connection string (i.e. including user name and password)?Tue, 15 Jan 2013 05:08:21 GMTAbu Dinahttp://www.sqlservercentral.com/Forums/Topic1407124-147-1.aspxYou can store package configurations in the database tooTue, 15 Jan 2013 04:35:17 GMTJayanth_Kuruphttp://www.sqlservercentral.com/Forums/Topic1407124-147-1.aspxThanks mate..its very useful info.Tue, 15 Jan 2013 04:34:37 GMTkarthick.alangattanhttp://www.sqlservercentral.com/Forums/Topic1407124-147-1.aspxThe 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.aspxTue, 15 Jan 2013 04:26:37 GMTSam Vangahttp://www.sqlservercentral.com/Forums/Topic1407124-147-1.aspxHow 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.Tue, 15 Jan 2013 03:15:12 GMTkarthick.alangattan