After Establishing a Connection to the data source, you can use the CData Jira Assets lookup component to do a lookup against Jira Assets and map the matched and unmatched rows to different outputs in your Data Flow task.

Performing a Lookup to Jira Assets Data with the Lookup Component

You can use the Lookup Component to perform a lookup on a specified set of columns in Jira Assets. This component takes one input and has two outputs: one for matched rows in Jira Assets and one for unmatched rows. The component provides two cache options which can affect the performance of the lookup but do not change the results of the lookup operation. These cache options are described later in this section.

1. In the SSIS Toolbox, drag the CData Jira Assets Lookup Component into the Data Flow.
2. Double-click the CData Jira Assets Lookup Component. The CData Jira Assets Lookup Component opens.
3. Navigate to the Connection tab. In the Connection manager drop-down list, select an available CData Jira Assets connection manager, or create a new instance if one is not already available.
4. Choose your Access Mode: "Table or View" or "SQL Statement". Select "Table or View" to use the GUI to select a table or view. Select "SQL Statement" to configure a statement of your choice.
5. On the Columns tab, configure the fields on which you want to perform the lookup. Click on a column in the Available Input Columns list and drag it to the column you want to look up against in the Available Lookup Columns box.
6. Optionally, you can select fields to include in the outputs by checking the boxes for each column in the Available Lookup Columns section. You have the option to add the field to your output as a new field or to overwrite one of the fields in the input.

Full Cache

The default cache mode for the Lookup Component is Full Cache. With this mode, the Lookup Component creates a temporary SQLite cache file as soon as the first input row is detected. The cache is populated with all the rows in the Jira Assets table, but only the columns that are selected in the UI. After the cache is built, each row in the input is looked up against this local cache. This mode is optimal when working with large sets of data that require many lookups.

Partial Cache

Partial Cache mode is similar to Full Cache, but instead of pulling the entire table initially, the Lookup Component batches 100 rows from the input and issues a query to the data source in the following form and caches only those results:

SELECT ... WHERE LookupField IN ('value1', ..., 'value100')

This mode is only possible if looking up a single column. This mode can improve performance if you are working with a small set of inputs, since caching the entire Jira Assets table is very expensive.