![]() If your target database is DB2 z/OS, Informix, and Oracle, you can also modify the storage parameters in the Indexes dialog. You can assign an index to a physical storage object in the Indexes dialog for a DB2 z/OS, Informix, Oracle, SQL Server, and SAP ASE database. You do not have to reassign the storage location for each index manually.Īfter you import indexes, you can view or modify the index properties, definitions, and table associations in the Indexes dialog. Therefore, you can recreate the database using the same storage assignments. When you import the index information from a server, the storage location information for each index is maintained. When you reverse-engineer a database, the name, definition, and parameters of each index that is defined on the server are imported. ![]() This section includes details about how the reverse engineering process works for different database objects. Save Database Queries to a Trace File Reverse Engineering Specific Objects Connect to a database and reverse engineer.Select the reverse engineering options.(Optional) Save database queries to a trace file.The following diagram illustrates the steps to reverse engineer a model from a database or a script:Ĭomplete the following steps to reverse engineer a model: You can review the queries after the reverse engineering process completes. When you reverse engineer a database, you can set a trace file to record the queries that are executed to retrieve objects. You can also choose to include or exclude these options during reverse engineering. You can select to treat RI triggers as model objects or use the forward engineering option to include RI triggers in the schema. You can include or exclude RI triggers in the reverse engineering process. You can use the table index definitions or column names to infer these keys and relationships. You can also infer some logical information including primary keys, foreign keys, and table relationships. ![]() For this reason, the resulting models can vary depending on the target database that is selected. However, the target databases vary in the amount of logical data model information that is included in the physical schema. You can derive all the major model information, except subtype relationships, because currently no SQL database management system supports it. For example, if the target DBMS supports foreign key declarations, the reverse engineering process derives identifying and non-identifying relationships and default role names. However, reverse engineering also derives information from the schema and incorporates it into the model. Most of the information that you reverse engineer is explicitly defined in the physical schema. Redesign the database structure to suit your requirements.To understand how the objects are related to each other and then to build upon itĪfter the reverse engineering process completes, you can perform the following tasks:.You cannot reverse engineer into a model that has objects in it.Ī database can be reverse engineered for the following reasons: Note: You can reverse engineer only into a blank model. This graphical representation can be a logical or a physical model. The modeling tool creates a graphical representation of the selected database objects and the relationships between the objects. Reverse engineering is the process of creating a data model from a database or a script. How to Reverse Engineer a Model from a Database or a Script
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |