Oracle SQL Developer Data Modeler is a free data modeling and design tool used to increase developer productivity by providing the means to develop logical, multi-dimensional, user defined data types, relational and physical data models. The tool provides full forward engineering, including engineering from Logical ERD models to Relational models and the reverse, importing from the Data Dictionary and DDL script generation. The Data Modeler imports from and exports to a variety of sources and targets, provides a variety of formatting options and validates the models through a predefined set of design rules.
Here is the list of key bugs fixed for this release.
34423443 - ISSUE WITH IDENTITY AND AUTOINCREMENT WHEN USING DEFAULT VALUE
Oracle SQL Developer Data Modeler runs on the following operating systems:
- Microsoft Windows
The following requirements must be met to install and run correctly:
If you have worked with the production release of SQL Developer Data Modeler 2.0, then you can save and reuse the default settings you made in the Tools > General Options menu, such as the Default Design Directory and Formatting Options. After installing SQL Developer Data Modeler, you can use the Import/Export function in the Tools > Preferences > Data Modeler menu to export/import the settings.xml file.
Data Modeler needs to be restarted if "Use Versioning functionality" setting in preferences is changed.
Note: Since version 4.2, Data Modeler doesn't maintain SVN properties thus it's not backward compatible with versions before 4.2 in regards to versioning functionality. It's recommended to use the same version of Data Modeler on all workstations when versioning functionality is used.
Change in Persistence
Multi-line properties like comments, notes, scripts, PL/SQL code are presented with CDATA section in XML elements. Changed is the way domains are saved and now they are in line with the way other objects are saved - as result there are some changes in formatting of related XML files.
Predefined RDBMS sites are no longer distributed in file defaultRDBMSSites.xml and will be removed from existing versions of that file.
Using Save As
If you want to open models built in SQL Developer Data Modeler 2.0 and 3.0, you must use "Save As" before you start making changes in the SQL Developer Data Modeler 23.1.
SQL Developer Data Modeler 23.1 can open designs created with 3.1.x version and save them in their original location however further maintenance of such design in Data Modeler 3.1.x version is not recommended due possible lost of information.
"Note" object is no longer represented by separate file in the file system - those files will be deleted upon saving of design.
PDF Generation is no longer supported in SQL Developer or SQL Developer Data Modeler. We recommend using the image or HTML exports, using the Reporting Repository for generating your own reports, or relying on a PDF printer driver.
Using the Reporting Repository
You can export your designs to a reporting repository. Read the online help or the FAQ for more information. There is a brief Oracle by Example tutorial that walks you through creating and accessing the reporting repository and running the reports. Search for "Data Modeler" in the Oracle Learning Library for all tutorials.
Standard reports can be generated in HTML format only. Custom reports can be generated in HTML, XLS and XLSX formats. PDF and RTF generations are no longer supported.
Oracle Designer Import
SQL Developer Data Modeler connects to and imports directly from the Oracle Designer repository.
The following is a list of supported imports from Oracle Designer
Comparing Logical Models
To compare two logical models, ensure you have one model open and then select File > Import > Data Modeler Design. You can now select the logical model for the comparison. Once you have made the selection, you are presented with the Compare Merge dialog.
Comparing Relational Models and Generation Alter DDL scripts
All passwords set in the physical model are encrypted when saving a design in the file system.
The Tools > Preferences >Data Modeler > Model > Relational >Default Foreign Key Delete Rule defines the delete rule when a new FK is created. If you create a model by importing a DDL script, then ensure the option is set as required before the import.
Adding a Design to a Subversion Repository
You can add your design to a Subversion repository using a few different approaches; either from within SQL Developer Data Modeler, or by using a separate client.
Adding a Design to a Git Repository
IMPORTANT: A design should be fully saved before commit, update and merge operations are done - the same apply for pull and checkout of branch when Git is used. It is recommended to close and reopen the design after update, merge, checkout or pull operations are completed, especially when conflicts are resolved. Do not save design during or after those operations.
For more information on using Subversion with SQL Developer Data Modeler see the Documentation.
Creating User Defined Design Rules and Transformations
SQL Developer Data Modeler allows users to build scripts for user defined design rules and transformations. Object properties are described in "datamodeler/datamodeler/xmlmetadata/doc" directory; use index.html.
The product provides a few samples as illustrations of user defined design rules and transformations. For more information see the Documentation.
From Other Modeling Tools
- Oracle Designer 9i and above
Oracle SQL Developer Data Modeler imports from:
IMPORTANT: Oracle does not ship the non-Oracle drivers.To access the non-Oracle databases, you need to download and add the drivers required.
To add the required drivers : Go to Tools > Preferences > Data Modeler > Third Party JDBC drivers
- Script file for supported Oracle Databases, Microsoft SQL Server and IBM DB2
SQL Developer Data Modeler is supported through My Oracle Support for all users with an Oracle Database support license.
You can use the documentation in the Oracle SQL Developer Data Modeler Help or access the online documentation.