|
|
|
When you reverse engineer a database, you import any existing physical storage objects, of a supported type, as part of a model. For example, when you reverse engineer an Oracle database, you import the names of any tablespaces already defined on the server. You can view a physical storage object imported into a new model and change its parameters in the same way you view or modify a physical storage object added directly to a model.
When you generate a database schema, you can add the physical storage objects defined in the model as part of the schema and generate the physical database tables and indexes in the specified storage objects. For example, if you forward engineer an Oracle database, you can add any tablespaces that you defined and generate tables in a particular tablespace according to the associations you have established in the Table Editor.
Whether you add physical storage objects on the server using CA ERwin Data Modeler or another tool, you can control the storage location for database tables generated by CA ERwin Data Modeler. In this way you can control how storage space on the server is utilized. If necessary, you can also tune database performance by modifying the parameters associated with a particular storage object, table, or index location.
Note: Not all databases support forward engineering of physical storage objects.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |