In addition to modeling the logical structure of your data systems, you can use PowerDesigner to specify the physical environment to which the database will be deployed.
Tablespaces and Storages (PDM)
Tablespaces and storages are generic objects used to represent physical locations (in named partitions) of tables and indexes in a database or storage device.
Lifecycles (PDM)
A lifecycle allows you to model the movement of data from expensive, rapid storage, through various forms of cheaper slower storage as the data ages and access requirements diminish. The period during which data remain in each kind of storage are modeled as phases, which are associated with tablespaces. The data movement itself is performed at the level of partitions.
Phases (PDM)
A phase defines the period of time that data governed by a lifecycle will be retained by a particular tablespace.
Partitions (PDM)
A partition is a physical division of the contents of a database table, created to improve manageability and performance.
Physical Options
A physical option is a parameter (included at the end of a Create statement) that defines how an object is optimized or stored in a database. Physical options are not supported by all databases, and vary by DBMS. In ASA 6, for example, you can define physical options for tables, columns, indexes, tablespaces, and databases. Other DBMSs provide options for keys, storages, and sequences.
Created October 7, 2009. Send feedback on this help topic to Sybase Technical Publications:
pubs@sybase.com