Logical-to-physical data model transformation object naming rules

When you transform a logical data model into a physical data model, certain rules are followed to generate the name of the physical data model objects.

On the Options page of the Transform to Physical Data Model wizard, you can specify some options for how the names of physical data model objects are generated. For example, you can specify whether to use upper or lower case characters, and you can specify whether logical object names or labels are used to generate physical object names or labels.

In addition to the wizard options, entity and attribute names are transformed to table and column names according to the following rules:
  • If an entity has a defined abbreviation property, the corresponding table is named according to the abbreviation property.
  • If an entity does not have a defined abbreviation property, the Transform to Physical Data Model wizard searches for the entity name in the glossary models that are specified for the project. If the entity does not have a glossary model name, or there is no glossary model specified for the project, then the entity name is used.
  • If parts of an attribute name match a domain name, then the corresponding parts in the column name are named according to the name of the domain property that the attribute references. If the referenced domain property uses an abbreviation, the abbreviation is used instead.
  • If an attribute has a defined abbreviation property, the corresponding column is named according to the abbreviation property.
  • If an attribute does not have a defined domain or abbreviation property, the Transform to Physical Data Model wizard searches for the attribute name in the glossary models that are specified for the project. If the attribute does not have a glossary model name, or there is no glossary model specified for the project, then the attribute name is used.

Feedback