MySQL Connector Guide > Mappings and Mapping Configuration Tasks with MySQL Connector > MySQL Sources in Mappings
  

MySQL Sources in Mappings

To read data from a MySQL database, configure a MySQL object as the Source transformation in a mapping.
Enable partitioning when you configure the Source transformation in the Mapping Designer to optimize the performance of the Mapping Configuration task.
Specify the name and description of the MySQL source. Configure the source, query options, and advanced properties for the source object.
The following table describes the source properties that you can configure for a MySQL source:
Property
Description
Connection
Name of the active MySQL source connection.
Source Type
Type of the MySQL source object available. You can choose from the following source types:
  • - Single
  • - Multiple
  • - Query
  • - Parameter
Object
Name of the MySQL source object.
Filter
Configure a simple filter or an advanced filter to remove rows at the source. You can improve efficiency by filtering early in the data flow.
A simple filter includes a field name, operator, and value. Use an advanced filter to define a more complex filter condition, which can include multiple conditions using the AND or OR logical operators.
Sort
Select the fields and type of sorting to use. To sort data for a parameterized source, you must use a parameter for the sort options.
Select distinct rows
When you read data from multiple sources, select this option to read only distinct rows.
The following table describes the advanced source properties that you can configure for a MySQL source:
Property
Description
Tracing level
Amount of detail that appears in the log for this transformation. You can choose terse, normal, verbose initialization, or verbose data. Default is normal.
Pre SQL
Pre-SQL command that must be run before reading data from the source.
Post SQL
Post-SQL command that must be run after writing data to the target.
Output is Deterministic
Relational source or transformation output that does not change between session runs when the input data is consistent between runs.
When you configure this property, the Secure Agent does not stage source data for recovery if transformations in the pipeline always produce repeatable data.
Output is repeatable
Relational source or transformation output that is in the same order between session runs when the order of the input data is consistent.
When output is deterministic and output is repeatable, the Secure Agent does not stage source data for recovery.