Table of Contents

Search

  1. Preface
  2. Using the Designer
  3. Working with Sources
  4. Working with Flat Files
  5. Working with Targets
  6. Mappings
  7. Mapplets
  8. Mapping Parameters and Variables
  9. Working with User-Defined Functions
  10. Using the Debugger
  11. Viewing Data Lineage
  12. Comparing Objects
  13. Managing Business Components
  14. Creating Cubes and Dimensions
  15. Using the Mapping Wizards
  16. Datatype Reference
  17. Configure the Web Browser

Maintaining Relational Target Definitions

Maintaining Relational Target Definitions

You can maintain relational target definitions in the following ways:
  • Reimport the target definition.
    Reimport a target definition rather than edit it if the target changes significantly.
  • Define primary key-foreign key relationships.
    Define primary key-foreign key relationships between relational target tables.
  • Edit the target definition.
    Edit a target definition to add comments or key relationships, or update it to reflect a changed target.
After you create a relational target definition, you can edit it using the following target definition tabs:
  • Table tab.
    Edit properties such as constraints for relational targets and flat file properties for flat file targets.
  • Columns tab.
    Edit column information such as datatype and precision.
  • Indexes tab.
    Add index information for relational target definitions.
  • Metadata Extensions tab.
    Extend the metadata stored in the repository by associating information with repository objects, such as target definitions.
When you change a target definition, the Designer propagates the changes to any mapping using that target. Some changes to target definitions can invalidate mappings.
The following table describes how you can impact mappings when you edit target definitions:
Modification
Result
Add a column.
Mapping not invalidated.
Change a column datatype.
Mapping may be invalidated. If the column is connected to an input port that uses a datatype that is incompatible with the new one (for example, Decimal to Date), the mapping is invalid.
Change a column name.
Mapping may be invalidated. If you change the column name for a column you just added, the mapping remains valid. If you change the column name for an existing column, the mapping is invalidated.
Delete a column.
Mapping may be invalidated if the mapping uses values from the deleted column.
Change the target definition type.
Mapping not invalidated.
When you add a new column to a target in the Target Designer, all mappings using the target definition remain valid. However, when you add a new column and change some of its properties, the Designer invalidates mappings using the target definition.
You can change the following properties for a newly added target column without invalidating a mapping:
  • Name
  • Datatype
  • Format
If the changes invalidate the mapping, validate the mapping and any session using the mapping. You can validate objects from the Query Results or View Dependencies window or from the Repository Navigator. You can validate multiple objects from these locations without opening them in the workspace. If you cannot validate the mapping or session from one of these locations, open the object in the workspace and edit it.


Updated July 02, 2020