Content deleted Content added
Improved some awkward wording in last sentence of abstract |
|||
Line 27:
; Parameters (SQL Server 2012 Integration Services): Parameters allow you to assign values to properties within packages at the time of package execution. You can have project parameters and package parameters. In general, if you are deploying a package using the package deployment model, you should use configurations instead of parameters.
; Precedence constraints: Tasks are linked by precedence constraints. The precedence constraint preceding a particular task must be met before that task executes. The run time supports executing tasks in parallel, if their precedence constraints so allow. Constraints may otherwise allow different paths of execution depending on the success or failure of other tasks. Together with the tasks, precedence constraints comprise the workflow of the package.
; Tasks: A task is an atomic work unit that performs some action. There are a couple of dozen tasks that ship in the box, ranging from the file system task (that can copy or move files) to the data transformation task. The data transformation task actually copies data; it implements the [[Extract, transform, load|ETL]] features of the product
; Variables: Tasks may reference variables to store results, make decisions, or affect their configuration.
| |||