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.
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.
Phases (PDM)
A phase defines the period of time that data governed by a lifecycle will be retained by a particular tablespace.
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.
Physical Options (PDM)
Physical options are DBMS-specific parameters that specify how an object is optimized or stored in a database, and are included at the end of the object's Create statement. Physical options are defined in the DBMS definition file, and may be available for tables, columns, indexes, tablespaces, and other objects. You can specify default physical options for all objects of a particular type and for individual objects (overriding the default, if one is specified).