|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Friday, April 26, 2013 1:47 AM
Points: 3,
Visits: 62
|
|
| 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.
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Friday, June 14, 2013 1:13 PM
Points: 42,
Visits: 268
|
|
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.
http://svangasql.wordpress.com
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Friday, April 26, 2013 1:47 AM
Points: 3,
Visits: 62
|
|
| Thanks mate..its very useful info.
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: Tuesday, May 07, 2013 6:43 AM
Points: 1,785,
Visits: 1,008
|
|
You can store package configurations in the database too
Jayanth Kurup
|
|
|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Today @ 10:26 AM
Points: 507,
Visits: 2,229
|
|
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)?
----------------------------------- http://www.SQL4n00bs.com
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: Tuesday, May 07, 2013 6:43 AM
Points: 1,785,
Visits: 1,008
|
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Monday, February 18, 2013 6:39 AM
Points: 19,
Visits: 74
|
|
| 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.
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Thursday, June 13, 2013 2:02 PM
Points: 198,
Visits: 656
|
|
| 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.
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Today @ 9:10 AM
Points: 232,
Visits: 671
|
|
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.
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Thursday, June 13, 2013 8:15 PM
Points: 162,
Visits: 437
|
|
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.
|
|
|
|