You can modify an object's properties from its property sheet. To open a table property sheet, double-click its diagram symbol or its Browser entry in the Tables folder.
|
Property |
Description |
|---|---|
|
Name |
Specifies the name of the item which should be clear and meaningful, and should convey the item's purpose to non-technical users |
|
Code |
Specifies the technical name of the item used for generating code or scripts, which may be abbreviated, and should not generally include spaces |
|
Comment |
Specifies a descriptive label for the table |
|
Stereotype |
Sub-classification used to extend the semantics of an object without changing its structure; it can be predefined or user-defined |
|
Owner |
Specifies the name of the table owner. You choose an owner from a list of users. A table can only have one owner at a time. This is normally the table creator |
|
Number |
Specifies the estimated number of records in the table in the physical database, which is used to estimate database size. This box is automatically populated during reverse engineering if you select the Statistics check box in the Reverse Engineering dialog box (see Reverse Engineering from a Live Database). You can enter your own value in this field, or refresh its statistics (along with those for all of the table's columns) at any time by right-clicking the table symbol or its entry in the Browser and selecting Update Statistics from the contextual menu. You can also update the statistics for all tables by selecting (see Reverse Engineering Database Statistics). |
|
Generate |
Specifies that the table is generated in the database |
|
Dimensional type |
Specifies the multidimensional type of the table. You can choose between:
|
|
Type |
Specifies the type of the table. You can choose between:
|
The Lifecycle tab is available if data lifecycle modeling (see Lifecycles (PDM)) is supported for your DBMS. These properties can be set for all the tables governed by the lifecycle on the lifecycle property sheet Tables tab (seeLifecycle Properties).
| Property | Description |
|---|---|
| Lifecycle | Specifies the lifecycle with which the table is associated. Select a lifecycle from the list or click the tools to the right of this field to create a new lifecycle or open the property sheet of the currently selected one. |
| Start date | Specifies the start date from which to generate the first partition. Click the Generate Partitions tool to the right of this field to create partitions for the table, based on the partition range and start date. |
| Partition range | [read only] Specifies the duration of the partitions that will be created for the table. This value is controlled by the lifecycle (see Lifecycle Properties). |
| Row growth rate (per year)/Initial Rows | Specifies an estimate of the increase of the size of the table per year, and the number of rows to start from as a basis for the calculation of cost savings. Click the Estimate Cost Savings tool to the right of this field to perform the calculation. |
| Cost Savings | This groupbox lists the cost savings that accrue to the storage of this table's data through its association with the lifecycle. Each line in the grid represents one year of savings, which are shown as a monetary value and as a percentage of the cost of storing the data statically outside of a lifecycle. |
The following tabs are also available:
Columns - lists the columns associated with the table (see Columns (PDM)).
Indexes - lists the indexes associated with the table (see Indexes (PDM)).
Keys - lists the keys associated with the table (see Keys (PDM)).
Triggers - lists the triggers associated with the table (see Triggers (PDM)).
Procedures - lists the procedures associated with the table (see Stored Procedures and Functions (PDM)).
Security Procedures - [data lifecycle modeling only] lists the procedures which control access to the table (see Stored Procedures and Functions (PDM)).
Physical Options - list the physical options associated with the table (see Physical Options).
Preview - displays the SQL code associated with the table (see Previewing SQL Statements).