The executable is C:\Program Files (x86)\WinSCP\WinSCP.exe and the Arguments I use are: -console -script="X:\Path\To\Script\WinSCPScript.txt" -xmllog="X:\Path\To\Script\WinSCP-!S-!Y-!M-!D-!T.log" -xmlgroups` The options on put are due to how the remote server works for the script I happened to grab. Put -nopreservetime -nopermissions -transfer=ascii file5.csv Put -nopreservetime -nopermissions -transfer=ascii file4.csv Put -nopreservetime -nopermissions -transfer=ascii file3.csv Put -nopreservetime -nopermissions -transfer=ascii file2.csv Put -nopreservetime -nopermissions -transfer=ascii file1.csv Lcd "M:\SSIS\eSchoolPlus to Clever\Output" Mine tend to look like this: # Set batch settings You also might want to specify option failonnomatch, but I haven't tested that one yet myself since I'm still on a slightly older version that doesn't support that option. Be sure to specify option batch abort and option confirm off. You can store it in the registry with WinSCP's session manager, but I believe that's a per-user registry which makes for lots of possible fun when you have the SQL Agent using an SSIS Proxy account.Ĭreate your script file with the commands you want to use. It has the disadvantage that you're storing the password in plain text. This has the advantage of working for FTP, FTPS, and SFTP. It's certainly the least Microsoft-y approach, but, IMX, it's more foolproof. There are also several third party extensions for SFTP and the like, but I don't use those. BIDS in 2008 has an FTP Task, but I never use it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |