Use this page to specify options for the transformation.
- Physical Name
- Specify options for transforming object names.
- Use upper case
- Select to specify that physical data model object names are created
using all uppercase characters. For example: TABLENAME1
- Use lower case
- Select to specify that physical data model object names are created
using all lowercase characters. For example: tablename1
- Use title case
- Select to specify that physical data model object names are created
using title case. For example: Tablename1
- Use existing case
- Select to specify that physical data model object names retain
the same case as the corresponding logical data model object names.
- Name source
- Use name
- Select to specify that physical data model object names are created
based on the name of the source logical data model object.
- Use label
- Select to specify that physical data model object names are created
based on the label of the source logical data model object. If you
select this option and there are data objects in the logical data
model without labels, names are used instead.
- Label source
- Use name
- Select to specify that physical data model object labels are created
based on the name of the source logical data model object.
- Use label
- Select to specify that physical data model object labels are created
based on the label of the source logical data model object. If you
select this option and there are data objects in the logical data
model without labels, names are used instead.
- Data type defaults
- Specify options for the default data type.
- Data type
- Specify a default physical data type. The default data type is
used as the physical data type in the following situations:
- The logical data type is not defined for an attribute.
- An attribute has an invalid logical data type.
- An equivalent physical data type cannot be resolved from the data
type mapping for the target vendor.
- Length
- Specify a default length value. The default length is used when
an attribute has a logical data type for which a required length was
not specified.
- Precision
- Specify a default precision value. The default precision is used
when a attribute has a logical data type for which a required precision
was not specified.
- Scale
- Specify a default scale value. The default scale is used when
a attribute has a logical data type for which a required scale was
not specified.
- Surrogate key
- Specify options for transforming surrogate keys. These options
might not be available if the target database vendor and version does
not support identity columns or sequences.
- Generate identity column
- Select to specify that surrogate keys are transformed to identity
columns.
- Generate sequence
- Select to specify that surrogate keys are transformed to sequences.
- Miscellaneous
- Specify additional options for the transformation.
- Copy
- Select elements from the logical data model that you want to copy
to their physical model element equivalents.
- Transform diagrams
Select to generate physical data model diagrams that correspond
to all logical data model diagrams in the context of the transformation.
If you do not select this option, you can manually create diagrams
after you complete the wizard.
Important: If you are
updating an existing physical data model and you select this option,
all existing physical data model diagrams in the context of your transformation
are replaced with new diagrams. For example, if you are transforming
from a package in a logical data model, all existing physical data
model diagrams that correspond to the context of that package are
replaced.
- Generate traceability
- Select this option to generate traceability between attributes
in the logical data model and the resulting columns in the physical
data model. These traceability dependencies will also be used to try
to pair renamed entities and tables or relationships and foreign keys
in the Compare editor. Traceability is maintained through dependencies
between the attributes and the columns that have a dependency type
of TRANSFORM_TRACEABILITY. These dependencies are owned by the columns
in the physical data model. If you generate traceability, you can
discover these dependencies by performing an analyze impact action
on the column or attribute.
- Column ordering
- Specify whether to place all key columns first in generated tables.
- Append new columns
- Available only if you are transforming to an existing physical
data model. Specifies that new columns are appended to the end of
the existing table's column list. If you do not select this option,
new columns are inserted into the existing table's column list
based on the new attributes' positions in the entity's attribute
list.
- Schema name
- Type a name for the physical data model schema. If you are transforming
to an existing model or using a template model, you can browse to
a target schema in the target model. Generated physical data model
elements are contained in the target schema, and relationships are
resolved to existing elements in the target schema. If you do not
specify a target schema, the default (root) target schema is used.
- Join table separator
- Type a separator for join table names. A join table is the physical
equivalent of a many-to-many logical relationship. Join table names
are composed of the names of the two tables that participate in the
relationship separated by a separator character. For example: Employee_x_Department.
- Roll up type table suffix
- Type a suffix for type table names. This string is used to create
type table names when the Transform as property
of a logical model generalization object is set to Roll Up.