Changing the Database Platform of a Model
Go Up to Creating and Working With Data Models
ER/Studio Data Architect lets you change the database platform of your physical model. When initially designing your database, you selected a database platform. Your choice of database platform can have a profound effect on development and administration issues. For example, the supported datatypes can differ drastically between database platforms, although ER/Studio Data Architect does convert them. In addition, indexing strategy, along with data storage and query optimization can differ greatly between different databases for the exact same physical model.
If you decide later in the design process that you need to change your database platform, you can use the Change Database Platform command.
- ER/Studio Data Architect supports all major database platforms. Also, it facilitates the translation between different database platforms with its datatype and DDL conversion facilities.
For a list of supported database platforms, see Supported Database Platforms.
Note: If you change to a database platform that does not support the schema objects in the selected model, you will lose those objects. For example, packages are supported in Oracle but not in IBM DB2 for OS/390. In this case, changing the Oracle model results in package definitions being lost.
- In the Data Model Explorer, click the physical model you want to change to a different database platform.
- Choose Database > Change Database Platform.
- Select the database platform and version and then click OK.
Notes
- ER/Studio Data Architect supports all major database platforms. Also, it facilitates the translation between different database platforms with its datatype and DDL conversion facilities.
- For a list of supported database platforms, see Supported Database Platforms.
- If you change to a database platform that does not support the schema objects in the selected model, you will lose those objects. For example, packages are supported in Oracle but not in IBM DB2 for z/OS, so in this case changing the Oracle model to a DB2 model results in the package definitions being lost.