December 11, 2017 at 2:30 pm
I am having a discussion as to ftp applications on sql server. My developers have putty and winscp installed because they are not able to sftp from ssis on the server with the integrated task. I have raised the argument that I dont feel that we should be adding aditional pieces onto the server for security purposes to keep the foot print small. But I cant really generate a great argument and am failing to find sources of documentation to support this. Is it ok to be running ftp tasks, have the putty executable and have ports open on the ssis/sql server?
December 11, 2017 at 3:12 pm
hmm... the footprint for adding winscp should be pretty small. I don't know why they would need putty on there just to transfer files(although that should also be a very small footprint). As far as security impact, your SQL Server is hopefully behind a firewall and it would be up to whoever manages that to set it up to allow access to wherever you're pushing the files to and if you're only pushing out files there would be no need open any ports up for incoming connections.
That said depending on your organization if you have some kind of dedicated file transfer process it might be easier to just write out whatever files and let that process take over without using SSIS to transfer anything.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply