Index Properties

Name/Code/Comment

Identify the object. The name should clearly convey the object's purpose to non-technical users, while the code, which is used for generating code or scripts, may be abbreviated, and should not normally include spaces. You can optionally add a comment to provide more detailed information about the object. By default the code is generated from the name by applying the naming conventions specified in the model options. To decouple name-code synchronization, click to release the = button to the right of the Code field.

Stereotype

Extends the semantics of the object. You can enter a stereotype directly in this field, or add stereotypes to the list by specifying them in an extension file.

Owner

Specifies the name of index owner. You choose an owner from a list of users, the index and table owners can be identical or different. An index can only have one owner at a time. This is normally the index creator.

Some DBMS allow you to define an index owner, either identical or different from the table owner. If the DBMS of the current model does not support index owners, the table owner will be automatically assigned to the index after switching to a DBMS that supports index owners.

Table

Specifies the table to which the index belongs.

Type

Specifies the type of index (if supported by your DBMS). For information about Sybase IQ index types, see Indexes (IQ).

Unique

Specifies that the index is a unique index.

Cluster

Specifies that the index is a clustered index. A table cannot have more than one clustered index.

Note that clusters in Oracle 11 and higher are modeled as extended objects with a <<Cluster>> stereotype (see Clusters (Oracle)).

Keywords

Provide a way of loosely grouping objects through tagging. To enter multiple keywords, separate them with commas.