JDBC V2 Connector > Mappings and elastic mappings in JDBC V2 Connector > JDBC V2 sources in mappings and elastic mappings
  

JDBC V2 sources in mappings and elastic mappings

When you configure a mapping or an elastic mapping to use a JDBC V2 source, you can configure the source properties.
Specify the name and description of the JDBC V2 source. Configure the source and advanced source properties for the JDBC V2 object.
You can parameterize the source and advanced source properties for the JDBC source object in a mapping or an elastic mapping.
The following table describes the JDBC V2 source properties that you can configure in a Source transformation:
Property
Description
Connection Name
Name of the source connection.
Source Type
Source type. Select one of the following source types:
  • - Single Object. Select to specify a single JDBC V2 object.
  • - Multiple Objects. Select to specify multiple JDBC V2 objects. Use the advanced relationship option to define the relationship for the objects that you want to join.
  • - Parameter. Select to specify a parameter name. You can configure the source object in a mapping task associated with a mapping that uses this Source transformation.
  • - Query. Select to define a valid and supported SQL query in the Source transformation.
Object
Source object for the mapping.
Filter
A simple filter or an advanced filter condition to remove rows at the source. You can improve efficiency by filtering early in the data flow.
Specify a simple filter by including a field name, operator, and value. Configure an advanced filter to define a more complex filter condition that can include multiple conditions using the AND or OR logical operators.
You can choose from the following filter conditions:
  • - Not parameterized. Use a basic filter to specify the object, field, operator, and value to select specific records.
  • - Completely parameterized. Use a parameter to represent the field mapping.
  • - Advanced. Use an advanced filter to define a more complex filter condition.
Sort
Not applicable.
The following table describes the JDBC advanced source properties that you can configure in a Source transformation:
Advanced Source Property
Description
Pre SQL
The SQL query that the Secure Agent runs before reading data from the source.
Post SQL1
The SQL query that the Secure Agent runs after reading data from the source.
Fetch Size
The number of rows that the Secure Agent fetches from the database in a single call.
Table Name
Overrides the table name used in the metadata import with the table name that you specify.
Schema Name
Overrides the schema name of the source object.
If you specify the schema name both in the connection and the source properties, the Secure Agent uses the schema name specified in the source properties.
SQL Override
The SQL statement to override the default query and the object name that is used to read data from the JDBC V2 source.
Tracing Level
Determines the amount of details that logs contain.
You can select one of the following tracing levels:
  • - Terse. The Secure Agent logs initialization information, error messages, and notification of rejected data.
  • - Normal. The Secure Agent logs initialization and status information, errors encountered, and skipped rows due to transformation row errors. Summarizes session results, but not at the level of individual rows.
  • - Verbose Initialization. In addition to normal tracing, the Secure Agent logs additional initialization details, names of index and data files used, and detailed transformation statistics.
  • - Verbose Data. In addition to verbose initialization tracing, the Secure Agent logs each row that passes into the mapping. Also notes where the Secure Agent truncates string data to fit the precision of a column and provides detailed transformation statistics. When you configure the tracing level to verbose data, the Secure Agent writes row data for all rows in a block when it processes a transformation.
1Applies only to mappings.
The remaining properties are applicable for both mappings and elastic mappings.

Joining multiple objects

When you create a Source transformation, you can select multiple JDBC V2 objects as the source type and then configure an advanced relationship to combine the tables.
    1. In the Source transformation, click the Source Type as Multiple Objects.
    2. From the Actions menu, select Add Source Object, and then select the source object that you want to add from the displayed list:
    3. Click Related Objects Actions menu, and then select Advanced Relationship to define the relationship between the tables:
    Note: The Add Related Objects option is not applicable.
    The following image shows an example of an advanced relationship condition defined between the JDBC V2 tables:
    You can view the relationship defined between the objects.
    If you join tables that are from different schemas, you must manually add the schema names.
    The following image shows an example of an advanced relationship condition defined between two JDBC V2 tables where the schema names are different:
    You can view the advanced relationship defined for the tables.

Rules and guidelines for joining multiple source objects

Consider the following rules and guidelines when you add multiple source objects: