I want to know the exact difference between FTP Task and File System Task i gone through some tutorials but i didn't get any major differences
Can anyone help me out with this
They give the same functionality but use complete different mechanics:
File System Task is used to handle local or network (accessible, mapped drives) files. You can also change files properties to hide a file or make it read-only.
FTP Task uses the File Transfer Protocol to interact with an FTP server to move, create or delete files. This protocol involves a lot of communication procedures and handling to do these operations.
For an FTP communication you need a client and a server (that is a software running all the time listening to communications on one end), while in the File System Task the SSIS just interacts to the OS file system directly.
Related
I have used InDesign server locally and in properties, it goes like
indesign.instance=http://localhost:20055and works fine.
Now I try to use instances running on a remote server and in properties it goes as follows:
indesign.instances=http://##.#.#.11:7700,http://##.#.#.11:7701,http://##.#.#.11:7702
and my app connects to the server where InDesign server instances are running. When I execute my script it fails with an error that the file does not exist or cannot find a directory. I understand that instance does not know anything about my file system. But I know for sure it can be connected.
Could you please advise me on the correct approach?
You could share the file system you are working on over a shared folder. Then your Client will place a file into the shared file system and the server can find it.
Or, if it is a remote server without any direct network access, build a document service to upload a file to the server over HTTP.
An ASP.NET application (running on Windows server/IIS 7) has to transfer big size files uploaded by current user to an external SFTP server. Due to the file size the idea is to do this asynchronously.
The idea is that the ASP.NET application stores the uploaded file on a local directory of the Windows server. The current user can continue his work. A Windows service or a Quartz job (other tools(*)/ideas?) is now responsible to transfer the file to the external SFTP server.
(*) Are there existing tools that listen on changes of a Windows directory and then move the files on a SFTP server (incl. handling communication errors/retries)?
If there is no existing solution, do you have had similar requirements? What do we have to consider? Because the connection to the SFTP server is not very stable we need an optimized error handling with auto retry functionality.
To watch for changes in a local directory in .NET, use
the FileSystemWatcher class.
If you are looking for an out of the box solution, use the keepuptodate command in WinSCP scripting.
A simple example of WinSCP script (e.g. watch.txt):
open sftp://username:password#host/
keepuptodate c:\local_folder_to_watch /remote_folder
exit
Run the script like:
winscp.com /script=watch.txt
Though this works only, if the uploaded files are preserved in the remote folder.
(I'm the author of WinSCP)
I would like to transfer a .txt file from a local machine (Windows 7 64-bit) to a Linux server.
The connection uses a passive mode and the task is set up with istransferascii = false
No matter, if I use variables or not for path destination, I face the same issue.
The task runs correctly and I receive the file into the remotepath but when I open the file, it is incomplete.
How to solve this problem and check if the file is complete?
I think the native SSIS FTP Task is not very useful.
I've used WinSCP successfully at a few sites. It seems quite reliable and has more functionality (e.g. SFTP, resuming) and much better doco and support. You can integrate it into SSIS using the Execute Process Task.
My favourite feature is that you can string a series of commands onto the command line - no need to mess with script files.
I'm fairly new to SSIS and am having trouble figuring out something that seems like it should be straight forward:
On server A, I have 10 files in "C:\SourceFiles\Patients" (these files are PDFs). I know the names of these 10 files and they won't change. Also, there is a server B which is the DB server and is where the SSIS package will be located. My goal is to loop through a DB table containing patients, add some patient data to the 10 source files (renaming the file) and then save this new file to server A.
I have most of this running already. Currently, all of this is happening in a script task using ADO.NET for the DB access (I'm already accessing the DB table on server B) and I'm accessing the source files on my local C drive.
I am having trouble figuring out how to specify server A in the Package Configuration for the source files. I have a file connection which specifies an existing folder (C:\SourceFiles\Patients), but it only specifies the location of the folder NOT the server. How to I specify server A for this file connection? Or, how do I use this file connection with a server A connection? I'm having real difficulty grasping this for some reason!!
The technologies I'm using are:
Visual Studio 2008,
C# in the SSIS script task,
ADO.NET in the SSIS script task and
SQL Server Management Studio 2008 (SSIS package will be imported here).
Thanks for pointing me in the right direction!
I see some issues with what you are trying to do.
PDF is an image format (an image of a document) and as such is not easily manipulated by SSIS. Generally if you are acting on a file from within SSIS, it would be a flat file of some sort, like a CSV or some other text format.
Using a script task to do all of your work within SSIS is failing to use the power of SSIS properly. If all you have in your SSIS project is a script task, you should just be using C# or VB.net directly and not involving SSIS in your project at all.
That all being said, you should access your files on server A using UNC (Universal Naming Convention) paths. You will need to pay close attention to your permissions within SSIS to make this work. When an SSIS job runs, it runs under a specific user, usually the SQL Server Agent user, and that user will need permissions to access the folder on server A remotely. When all of these permissions are set correctly, you can use something akin to \\ServerA\ShareName\Patients\ as the pointer to your directory with pdf's in it.
How do I set up a scheduled job in SQL Server 2008 that connects to a ftp server and transfers a file either to a local drive or even better into a table.
I think I can use SSIS (at least that I read) but can't find a tutorial or like.
If I can just get the file to my local drive then I good but of course the even better solution is a file transfer directly into a table :)
Definetely possible with SSIS.
Use Business Intelligence Studio to design the SSIS package, then you can schedule this package as SQL Agent job.
SSIS can't transfer it directly to the table, but it can download it to temporary file (use FTP task), then load it to table (depends on file format, most likely you'll need to use Data Flow task), and delete file (File System task).