Use the default execution mode when the source data store meets all the schema requirements described in the section Schema Requirements of chapter Requirements of the Readme .
Use the parallel mode when you want to execute more than one method simultaneously.
Warning: Use of the parallel mode where multiple methods access the same tables within the target data store(s) is not currently supported.
In order to run a parallel execution, the files created after a successful export from Data Masking or Data Subset Extraction must be stored in a different data directory for each method.
For more information about the default config directory, see the section Extension Technology Directories in this guide.
See Invoking Extension Technology for more information.
For more information about default directories, see the section Data in the chapter Extension Technology Directories.
In unload mode, the same schema requirements apply (as described in the section Schema Requirements of chapter Requirements of Readme ) , but with a difference: Data Express does not use privileges against the source data store. Instead, information is unloaded from the source data store to separate staging data store where these privileges are can be authorized.
You can use unload mode for the following two scenarios:
Source Data Store | Staging Data Store | Target Data Store |
---|---|---|
Data Store A |
Data Store B |
Data Store C |
Data Store A |
Data Store C |
Data Store C |
These examples show that the staging data store may or may not be the actual target data store.
For example, to use unload mode with Data Masking:
For more information about the Distributed Loader, see the section Using Distributed Loader of Part 2. Using Distributed Data Stores with Data Express.
For more information, see Enable Masking within the section Data Masking of Part 4: Data Express for Distributed Data Stores Tutorials.
For more information, see the section Invoking Extension Technology.
The data from the source data store is extracted and inserted into the staging data store after the required tables were created.