|
|
|
Forum Newbie
Group: General Forum Members
Last Login: Thursday, March 11, 2010 12:46 PM
Points: 2,
Visits: 105
|
|
| that's how its designed. it doesnt save setting like the passwords. you have to create a configration file and plug in the server name, server password, etc. There is a toolbar at the top of the designer screen. Click SSIS, Package configurations, enable package configs, and then create a config file.
|
|
|
|
|
SSC Rookie
Group: General Forum Members
Last Login: Yesterday @ 3:31 AM
Points: 35,
Visits: 56
|
|
|
|
|
|
Forum Newbie
Group: General Forum Members
Last Login: Monday, March 15, 2010 10:02 PM
Points: 1,
Visits: 2
|
|
| wow i read thru this thread looking for info on a looping ftp task and i realized that lots of posters dont understand the password security built into SSIS. Basically i think that everyone who recommends configuration files as a workaround to a "problem" with FTP misses the most obvious reason their packages fail 'encrypted keys'. MS in an attempt to appear to increase security made it nearly impossible to have unencrypted passwords. So if you put in the password in the ftp connection manager and then come back to it, it looks like it is gone, but it is not gone because VS has encrypted it with a user key. Why is this important? because it is often unlikely that you the package creator is the same user who executes the the job step from the package. Why does that matter? the agent doesnt have the same user key you do. Set up a log file for your package and it will indicate the user who executes each step, and that user has to be the user who builds the package. thats by far easier than configuration or script task. :~D
|
|
|
|
