This document is a list of the main new features added to SQL Developer Data Modeler 3.0. Most significant additions to the product are:
Below is the list of general new features. For a list of all current product features see Data Modeler Feature List
|Browser Navigator|| |
The browser navigator supports the ability to have multiple open designs.
|Custom Design Rules|| |
Create user-defined Design Rules.
Settings are available at the diagram level
|Domains||Added “Default value” property at domain level. The default value can be changed at column/attribute level. List of values defined at domain, column or attribute level is used to pick-up default value. |
Domains can be used in definitions in Data types model.
|Forward Engineering||There is a change in the way the engineering to the relational model works. The default status for new candidate key is "selected" now |
Unique index is created for One-to-one relationships defined in the Logical model if there is no PK/UK constraint or unique index defined over foreign key columns.
|Glossary||Create a glossary based on an existing design. Select Logical model > Create Glossary from Logical Model. |
Support for plurals added to the glossary. These are used in the name transformation and validation for entities and tables
Importing CA Erwin Data Modeler files has been extended to include the import of Erwin 7.x files.
|Physical Model|| |
Support for the import and DDL generation of packages and functions.
The settings.xml file used to store preferences is no longer used. Preferences still can be imported from the existing settings.xml file
|Relational Model||Added support for auto increment and identity columns in the Relational model. This is supported with sequences and triggers in the Oracle physical model. |
Support for dynamic properties – can be created and modified using UI and/or transformation scripts.
|Reporting.||Reporting provided through either: |
- Reporting Repository. Users export designs to a reporting repository and use SQL Developer to run reports.
- Local Reports: Run reports from the tool itself. Reports are word xml documents and can be opened in MS Word 2003 (or later). These reports include entities tables, domains and glossary.
|Reporting Repository||Support extended to include data types and process models. |
Note: If you export to the reporting schema in Data Modeler 3.0, either create a new schema or apply the upgrade script to the schema repository created by Data Modeler 2.0. (See Reporting Repository section in the release notes.)
|Subversion Integration|| |
Integrated version control using Subversion for complete design.
Table to View wizard creates views based on tables in a selected relational model.