PowerDesigner provides default model checks to verify the validity of tables and views.
Check |
Description and Correction |
---|---|
Name/Code contains terms not in glossary |
[if glossary enabled] Names and codes must contain only approved terms drawn from the glossary.
|
Name/Code contains synonyms of glossary terms |
[if glossary enabled] Names and codes must not contain synonyms of glossary terms.
|
Name/Code uniqueness |
Object names must be unique in the namespace.
|
Name and code length |
The table and view name and code length is limited by the maximum length specified in the DBMS definition (MaxLen entry, in the View categories) and in the naming conventions of the model options. and
|
Constraint name conflicts with index name |
[tables only] A constraint name of the table cannot be the same as an index name.
|
Existence of column, reference, index, key |
[tables only] A table should contain at least one column, one index, one key, and one reference.
|
Number of auto-incremented columns |
[tables only] Auto-incremented columns contain automatically calculated values. A table cannot contain more than one auto-incremented column.
|
Table index definition uniqueness |
[tables only] Identical indexes are indexes with the same columns, order and type. A table cannot have identical indexes.
|
Table mapping not defined |
[tables only] When a table belongs to a model containing one or several data sources, it must be mapped to tables or views in the data source in order to establish a relational to relational mapping.
|
Column mapping not defined |
[tables only] When a column belong to a table in a model containing one or several data sources, it should be mapped to columns in the data source in order to establish a relational to relational mapping.
|
Existence of permission |
Permissions are usage restrictions set on a table or view for a particular user, group or role.
|
Existence of partition key |
[tables only] A table managed by an age-based lifecycle policy must have a column specified as its partition key.
|
Invalid start date setting |
[tables only] A table managed by an age-based lifecycle policy must not have a start date earlier than the start date of the lifecycle.
|
Missing lifecycle policy |
[tables only] A table managed by a lifecyle must not reference tables not managed by a lifecycle.
|
Invalid mapping from source table |
[tables only] In a lifecycle where the first phase references an external database, each archive table must be mapped to exactly one external table.
|
Partial column mapping of source table |
[tables only] In a lifecycle where the first phase references an external database, all columns in each source table must be mapped to columns in the same archive table.
|
Existence of partition key mapping |
[tables only] In a lifecycle where the first phase references an external database, the partition key column in the archive table must be mapped to a column in the source table.
|
Tablespace outside lifecycle |
[tables only] A table managed by a lifecycle must be assigned to a tablespace associated with the lifecycle.
|