Task Factory Loews Corporation
"We bought the product mostly because of the company's reputation for the service they provide and the specific need of a secure SFTP task."

Matt Cushing

Application Systems Analyst/Developer

Loews Corporation

Greater New York City Area

Task Factory - Mark Marinovic
"We bought Task Factory primarily for the SCD Type 2 task, as it enabled us to do several things the built-in SSIS SCD task did not do. Task Factory comes highly recommended from me as our ROI was reached in just days."

Mark Marinovic

Task Factory - Urban Outfitters
"We have found that Task Factory tremendously speeds up the development process and improves performance by means of the high-performance components."

Tim Harris

BI Data Engineer

Urban Outfitters Inc.

Task Factory - Jay Cole
"I purchase Task Factory over a year ago, and let me tell you, IT WORKS FLAWLESSLY. I haven’t had a single problem with it, and I used to HATE having to make changes with the version you’re using. My advice (for what it’s worth) is to pay the money!"

Jay Cole

Task Factory
"I have found Task Factory to be a huge time saver with SSIS development. The SalesForce components alone saved close to two months of work on a major integration project. I highly recommend!"
Alan Rubel
Database Administrator
Joint Commission Resources


Buy Now Free Trial Download Compare Editions More Features

Task Factory Advanced Execute Process Task

The Advanced Execute Process Task provides a way for you to execute commands as if you were using the command line utility in windows.

Feature Highlights

  • Commands are executed as if you're using the command line
  • Can be used to call basic command functions like del, copy, ren, etc.
  • There can be multiple commands per instance of the Advanced Execute Process Task unlike the native SSIS execute process task
  • Commands can use variable replacement without the use of expressions
Advanced Execute Process Task

Advanced Execute Process Task - Step 1
The Advanced Execute Process Task is used to execute commands as if they were being executed from a command window. This allows for the use of basic command like copy, ping, del, etc as well as using any executable you'd like to be executed within SSIS. One of the best features is it allows for multiple commands per instance of the Task.

The Advanced Execute Process Task is used to execute commands as if they were being executed from a command window. This allows for the use of basic command like copy, ping, del, etc as well as using any executable you'd like to be executed within SSIS. One of the best features is it allows for multiple commands per instance of the Task.

Advanced Execute Process Task - Step 2
You are able to add multiple "Steps" to the advanced execute process. A step is a single command that mimics what would be executed from the command line.

Toolbar


The toolbar is used to control the steps for the Advanced Execute Process.

You are able to add multiple "Steps" to the advanced execute process. A step is a single command that mimics what would be executed from the command line.

Toolbar


The toolbar is used to control the steps for the Advanced Execute Process.

Advanced Execute Process Task - Step 3
Clicking the "Add New Step" button will bring up the "Add New Process Step" form.

Clicking the "Add New Step" button will bring up the "Add New Process Step" form.

Advanced Execute Process Task - Step 4

Step Name - The name of the current step

Step Command - The command in which this step will execute. The command can use any variables that are part of the package as replacement values in the command. For instance, if "User::strVHDFilePath" had a value of "C:\ssis\myserver.vhd" when the command in the step above was executed the full command would be "del c:\ssis\myserver.vhd".

Timeout (Second) - The number of seconds you'd like this step / command to run before the process is killed. Setting the value to 0 means there isn't a timeout.

Success Exit Code - The exit code of the command which indicates the step was successful.0 is the default success code for the command line.

Window Style - The style in which a command window is shown. The four options are Hidden, Normal (show a normal window), Minimized (show a command window minimized) and Maximized (show a command window maximized)

Standard Output Variable - You can either have the output of command outputted to the command window (will go to the BIDS execution results or log if the window style is hidden) or store the output in a variable. This is useful if you are going to use the output from the command in a later task or command step.

Error Output Variable - You can either have the error output of command outputted to the command window (will go to the BIDS execution results or log if the window style is hidden) or store the output in a variable. This is useful if you are going to use the erro output from the command in a later task or command step.

Step Description - You can store notes about the step here. When you enter a description here, it will show up when the step is selected in the main ui as shown below.

Step Name - The name of the current step

Step Command - The command in which this step will execute. The command can use any variables that are part of the package as replacement values in the command. For instance, if "User::strVHDFilePath" had a value of "C:\ssis\myserver.vhd" when the command in the step above was executed the full command would be "del c:\ssis\myserver.vhd".

Timeout (Second) - The number of seconds you'd like this step / command to run before the process is killed. Setting the value to 0 means there isn't a timeout.

Success Exit Code - The exit code of the command which indicates the step was successful.0 is the default success code for the command line.

Window Style - The style in which a command window is shown. The four options are Hidden, Normal (show a normal window), Minimized (show a command window minimized) and Maximized (show a command window maximized)

Standard Output Variable - You can either have the output of command outputted to the command window (will go to the BIDS execution results or log if the window style is hidden) or store the output in a variable. This is useful if you are going to use the output from the command in a later task or command step.

Error Output Variable - You can either have the error output of command outputted to the command window (will go to the BIDS execution results or log if the window style is hidden) or store the output in a variable. This is useful if you are going to use the erro output from the command in a later task or command step.

Step Description - You can store notes about the step here. When you enter a description here, it will show up when the step is selected in the main ui as shown below.

Advanced Execute Process Task - Step 5
One of the unique features of the Advanced Execute Task is it's ability to more than one command per instance of the Task. You can also tell the task what order to execute the steps / commands by using the Move Step Up and Move Step Down button that were seen above.

One of the unique features of the Advanced Execute Task is it's ability to more than one command per instance of the Task. You can also tell the task what order to execute the steps / commands by using the Move Step Up and Move Step Down button that were seen above.

View Our Suite of Pragmatic Works Products
Copyright 2014 by Pragmatic Works