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. POWERCENTERHELP
  17. Datatype Reference
  18. Configure the Web Browser

Editing Table Options

Editing Table Options

You can edit the following options on the Table tab of the target definition:
  • Business names.
    Add a more descriptive name to the table using the Rename button.
  • Constraints.
    SQL statements for table-level referential integrity constraints. Applies to relational targets only.
  • Creation options.
    SQL statements for table storage options. Applies to relational targets only.
  • Description.
    Add a comment or link to business documentation. These are displayed in Repository Manager for the target table. Adding comments or business documentation links to targets is an easy way to document the purpose of a target. You can add or modify comments to any existing target.
    You can enter up to 2,000 bytes/K in the description, where K is the maximum number of bytes a character contains in the selected repository code page. For example, if the repository code page is a Japanese code page where K=2, each description and comment field can contain up to 1,000 characters.
  • Keywords.
    Keep track of target definitions with key words. As development and maintenance work continues, the number of targets increases. While all of these targets may appear in the same folder, they may all serve different purposes. Keywords can help you find related targets. Keywords can include developer names, mappings, or the associated schema.
    Use keywords to perform searches in the Repository Manager.
  • Database type.
    Define the target type, either a relational database or a flat file. You can change a relational target definition to a flat file target definition and vice versa. When you change the target definition type, you lose some metadata when you save the changes to the repository.
    When you change the target definition type from relational to flat file, you lose indexes information, constraints information, and creation options information. The Workflow Manager invalidates all sessions using the target.
    When you change the target definition type from flat file to relational, you lose all flat file property information. If you change the target definition back to a flat file, the Designer uses default values for the flat file properties. The Workflow Manager invalidates all sessions using the target.
    If you change the target type from flat file to relational, the Workflow Manager invalidates all sessions that use the target. However, you can change a target type from relational to flat file without invalidating sessions that use the target.
  • Flat file information.
    When the database type is flat file, you can define the flat file properties by clicking the Advanced button.
To add options to a relational target definition:
  1. In the Target Designer, double-click the title bar of the target definition.
    The Edit Tables dialog box appears.
  2. Click the Rename button to edit the target name and the business name.
  3. To change the target type, choose a different database in the Database Type field.
    To change the target type to a flat file target, choose flat file.
  4. Edit the following properties for relational target definitions:
    • To add a constraint, type the SQL statement in the Constraints field.
    • To add a creation option, type the SQL statement in the Creation Options field.
  5. To add a description, type a description in the Description field.
  6. To add keywords, click Edit Keywords.
    The Edit Keywords dialog box appears.
  7. Use the buttons to create and move keywords.
  8. Click OK.


Updated June 25, 2018