Data Masking Components: Load Dictionary

{TOC}

SSIS Load Dictionary Component

API Reference, CLR Reference (links)

Usage Instructions:

Purpose

The purpose of the Load Dictionary component is to create a custom dictionary of values for the later use in Dictionary Substitution component. If the data schema includes certain elements that could not be masked using substitution components with pre-packaged data sets such as names or companies, than this particular component allows to create a set of (key,value) pairs in memory. Dictionary Substitution component picks up the values and replaces them with the substitution algorithm. Examples might include creating sets of "languages" from the language table, or "brands" from the brand table in the database, etc.

Algorithm

While none of the data masking algorithms are applicable, Load Dictionary simply retrieves a data set from the indicated source and makes it available via Object type variable.

Description

Load Dictionary component retrieves the key and the corresponding data field values from the data source, be it a table in a database or a file, and places the set of (key, value pair) into predefined Object Variable to be later used in Dictionary Substitution Component.

API Reference, CLR Reference (links)

Usage Instructions:

1. Configure a source that contains the id column and the column you want to create a custom data set from. The picture example is a table of colors with "picture Id" column as an id column and "color" as data value field.
2. Drag and Drop Load Dictionary data masking component, and connect the source and the Load Dictionary component.
3. Now, the data flow path(the blue arrow) passes proper meta-data to the Data Dictionary component. If you click on constraint, you will see:
4. Now that the metadata for the Data Dictionary exists, and values are passed into the data masking Data Dictionary component, please open the component editor. In the custom properties of "Library Variable Name", please choose the variable of the object**object typetype** that will hold data values as the dictionary. These values are the set that you customarily created.
5. In the second tab, there"Input areColumns", inputplease columns.check Please check-mark only one column,both the oneId thatcolumn youand willthe bedata masking with Generic Alpha Numeric algorithm: column:
6. ThisNow, we need to hint SSIS which column values will createbe anloaded extrainto the variable. In the third tab, "Input and Output Properties", expand input columns, highlight the column withcontaining the prefixdata “Masked_”.value ( in our case, it is "color"), and set its LoadColumn property to "True"
7. CreateNow awe connectionare managerdone forwith configuring the destinationData andDictionary. configureWe sourcewill componentnow forstart second part of the destination.Dictionary InSubstitution Algorithm: the connectionsubstitution manager, in the tab “Mappings”, specify that you want newly created Field_Masked to be a field replacing the original value. For that, just click on the available input columns, choose the masked value, and map to the “Available Destination Columns”
8. Now, all the configurations are complete for the valid values. You can run the package with the Generic AlphaNumeric Dynamic Data Masking component, and see the results of data masking:	itself.

Error Handling

9.8. If,There however,is thereno are invalid values in the package's source, one would need to configure error handling. Invalid values are those that are not conforming to the rules of the entity. To handle invalid values, each data masking component hasspecific error handling precedence constraint. One needs to create error destination connection and connect red arrow (error handling constraint) withfor this destination. As the connection is made, one needs to configure the state of failure: “Fail”,”Ignore” or “Redirect”.	component.
10. It is recommended that one re-directs the output into the error destination, so that later one be able to analyze and process data for quality purposes. The Generic Alpha Numeric components errors are the only ones not recommended for further processing as it is truly hard to break their format.
11. It is our suggestion that with Generic Alpha Numeric component one should not process erroneous data without further analysis at all.

Download Example ###**