S2.11.2 - SSIS Tutorial - Output Task

Output task

The SSIS Output task enables you to output your source fields and fields generated by the other matchIT SQL SSIS tasks in your package, to a single SQL table or comma delimited text file.

As demonstrated above, you would typically position the Output task to run after your other matchIT SQL tasks. This will ensure that the generated fields have all been populated, when the Output task runs.

Select from Available Tasks

When you open the Output task, Select from Available Tasks is the first tab you will see. This tab displays the preceding tasks.  By selecting a task, the fields generated by that task will be available to select for output in the next tab.

Note - if you have multiple Generate Keys tasks preceding your Output task (E.g. if you are performing an Overlap), you will be prompted to select the Data Source you wish to base the output on.

Select from Available Fields

In this tab, you can select the fields you wish to include in your output file/table. 

The source fields that you mapped from your source table(s) are listed first.  Next are the generated fields (I.e. fields generated by each of the preceding tasks).  

Generated fields will only be displayed for tasks that you have selected in the previous (Select from Available Tasks) tab.

Output Options

In this tab, you can select the format of the output; either Text File (Comma) or SQL Table.

If you choose to output to Text File, you can specify the destination of the file by clicking on the ellipses button. Otherwise, when outputting to a SQL table, simply type the name of the new table into the SQL Table Name box (the new SQL table will be created in the same database as the source tables.

Use Best Address

As described in the tab, this enables you to override your input addresses with improved addresses generated by matchIT SQL tasks. By using this option, you will ultimately end up with a single set of address fields where each address is the best version available (most up to date or correctly formatted), rather than just having multiple sets of address fields generated by the various tasks.

You can choose which tasks to take new address lines from by checking the relevant check boxes. You can also set the priority of the tasks based on which types of generated addresses you regard as being most valuable. 

E.g. by accepting the default options (as displayed above) if a record has a new address returned by the SuppressionConfiguration task (by hitting against a movers file), then that address will be taken first.  If it doesn’t, then a PAF validated address from the GenerateCorrectedAddresses task will be taken.  Finally, if the record failed to achieve PAF validation, then the correctly formatted/cased version of the address (generated by the GenerateKeys task) will be taken.

Note – to use these options, your input address lines must be labelled Address1, Address2, Address3, etc.