Creating a database diagram can be done through one of the following wizards available:



When importing a database there are a number of options that can make the import result to be somehow different:


    • Use 'do not import sequences' if not interested in complete database definition but only data structures and relations
    • Use 'infer table relations' if you like the import wizard to look for possible relations between imported database tables. The algorithm used to infer table relations works only with primary keys (indexes), for each table where a primary index is defined the engine will look if the fields that are part of the index are found in any other table - the match is done using the name and data type, if all fields part of the index are found a relation is created between the parent table (the one where the primary key is defined) and the child using the primary key fields as field mapping. The relation name pattern as well as default cardinality and delete action used on import can be set in preferences.
    • Use 'partition database by area' if database tables are actually 'grouped' in areas so the diagram will be partitioned in sub-diagrams, one for each database area defined. If that option is used no table will be visible in the main database diagram, the corresponding database area sub-diagram (partition) can be open to see tables that are allocated to that area. If all tables are using the default 'schema' area then it might be better to just not use partitioning option as all tables will be loaded in the same diagram anyway.