Table Triggers - Select to import Trigger definitions on Tables.Check Constraints - Select to import Check Constraint definitions on Tables.Unique Constraints - Select to import Unique Constraint definitions on Tables.Indexes - Select to import Table Indexes.Foreign Keys - Select to import Foreign Key definitions on Tables.Primary Keys - Select to import Primary Key definitions on Tables.The available options are briefly described here select the checkbox against an option to activate it. Values changed on this screen are saved to the registry so that they are re-applied in the next work session. The ' Filter Options' panel controls what object types and properties are read in from the database schema. If you suspect that the schema list might have changed since you loaded them, you can refresh the list by clicking on the Reload Schemas button. (You can click on the All button to select all the schemas, or the None button to clear all selected checkboxes.) Select the checkbox against each schema to include in the import. The available schemas are automatically listed in this panel. If the database type supports multiple schemas (such as SQL Server, Oracle, PostgreSQL and DB2 Express) you can filter objects to be retrieved from the database by schema. If you want to specify a different Package, click on the button and select an alternative Package. This field shows the target Package that the new objects will be saved to. If necessary, click on the button and, on the 'Machine Data Source' tab of the 'ODBC Select Data Source' dialog, select an alternative ODBC connection. This field shows a description of the current ODBC connection, in the format: The sophisticated reporting engine can produce high quality documentation, including data dictionaries, diagrams and relationships back to other models such as architecture and information requirements, and ultimately to business goals and drivers.ĭatabase schema information can be imported via the Database Builder or from the 'Code' ribbon. When systems target multiple DBMSs, these can all be reverse engineered into a model and elements and datatypes can be compared between these models. Once the schema is in Enterprise Architect, the database objects can be traced to other elements, ensuring the integrity of design and architecture. Enterprise Architect communicates with the DBMS via ODBC, can import a schema via this connection, and can synchronize the model with the live database if it is changed. A wide range of database objects are supported including Tables, Views, Procedures, Functions and Sequences. Enterprise Architect can reverse engineer a DBMS schema and its objects into a model under a number of different standards, including UML, Information Engineering and IDEF 1X. Being able to view the database schemas alongside other models of a system provides great clarity and reduces the chance of error. The power of model-based engineering is the ability to visualize, analyze and design all aspects of a system.
0 kommentar(er)
