➤➤ Move File: Moves a specific provided source file to a destination. You must indicate whether
the task should fail if the destination file already exists.
➤➤ Rename File: Moves a specific provided source file to a destination by changing the name.
You must indicate whether the task should fail if the destination file already exists.
➤➤ Set Attributes: Sets Hidden, Read-Only, Archive, or System attributes on a provided source file.
One benefit that may not be apparent in these functional descriptions is that the creation of directory
structures does not have to be made recursively. For example, you may create the path named
c:ssis asksmy file system task using the Create Directory form of the File System Task
by simply providing the path. You don’t have to create each part of the directory separately, as you
did in the DTS legacy product. This capability greatly reduces the typical file operation coding to a
simple configuration task for directory operations. However, don’t assume that you can do the same
with a file-level operation. If you attempt to rename a file from c:ssis to c:ssismy archive
and the folder my archive doesn’t exist, you will get an error that the path is not found.
Another feature of this task that may not be apparent is that it is written for a single operation. This
is by design. If you need to iterate over a series of files or directories, the File System Task can be
simply placed within a Looping Container. By keeping the task granular and singularly focused, it is
simplified and easily reused.
Most of the properties in this task are set in the General tab of the File System Task Editor
(see Figure 3-9). The contents of this tab may vary widely according to what you set in the
Operation property. These options correspond to specific file operations that the task can perform.
Once the option is set, you may be prompted to complete other properties not shown in this figure.