Oracle SQL Developer Data Modeler 3.3

New Features

March 2013

This document is a list of the main new features in SQL Developer Data Modeler 3.3.


Filtering of properties – can be set which properties per object type should be considered in compare/merge functionality.
Storage properties (defined in storage template) can be compared and alter statement generated.
Filtering on storage properties can be set. DDL configuration can be loaded providing settings for "Generate In DDL" filter.
Tabular view (in addition to tree presentation) for better tracking of changes, filtering by object type and status, regular expressions can be used in filtering. Report for modified, new and deleted objects can be generated. Similar functionality is used also in engineering between logical and relational models.

DDL Generation

Options to generate default values (default values normally are not included in DDL) – schema, tablespace, logging, storage as global option, options for each storage element.
Table and column level check constraints can be excluded from generated DDL – generate in DDL flag for each constraint.
Save current DDL generation settings (including selected objects and check constraints, name substitution and other DDL related settings) into configuration file.
Load DDL configuration settings from file.
Option to preserve DDL generation settings when DDL File editor is started and to restore them back when it’s closed.
SQL Developer Formatter can be used to format generated DDL – set as default formatting in preferences.
SQL Developer Formatter options appear in preferences.


Possibility to show/hide foreign keys and relationships in subviews.
Lines for self referencing foreign keys and relationships can be arranged.
Support for hiding Table and Entity elements.
Grid size can be changed in preferences.

Import and Export

Import from Designer Repository - Imported objects have the same ID as in Designer repository.
Export to Data Modeler Design - export configuration can be defined and used allowing easy slicing of the design.
Open Design - select relational models dialog is changed, default physical model can be set to be open, settings are used als in next “open design” operation.

Logical Model


  • Support for transferability added
  • Can be bound to natural key or set to use surrogate key during engineering to relational model – foreign key attributes are not maintained in latter case
  • Delete rule property of generated foreign key solely depends on relationship’s delete rule property
  • Support for relationship attributes – transformed to columns during engineering to relational model, dependent columns constraint for optional one to many relationship is also created

Support for surrogate keys during engineering to relational model – can be set on each entity. Domain or precision for Numeric logical type can be set in preferences and will be used when column is created.
Entity hierarchies – more flexible transformation to relational model with mixed engineering strategies based on “engineer” flag and subtypes setting for each entity in the hierarchy:

  • Single (super-type) table implementation with discriminator column and related existence dependency constraint
  • Tables for subtypes
  • Super-type and subtypes implementation with identifying foreign keys discriminator column and arc at parent table with supporting arc constraint
  • Arc implementation - Super-type and subtypes implementation where super type is child table with foreign keys in arc to subtype tables
  • Mixed implementation
Multidimensional Model

Export to “Oracle AW” now supports Oracle 11g OLAP, Oracle 10g OLAP is not supported any more.
Support for role playing dimensions in export to Oracle AW.
Level descriptive attributes can be created without mapping to attribute in logical model.
Extended definitions for search and dynamic reports functionality.
Sample design is included in distribution.
Multidimensional model can be bound directly to relational model.

Naming Standards

Template for surrogate key and surrogate key column.
Template for discriminator column created during engineering to relational model.
Template for “Automatic indexes” generated for PK, UK and FK constraints.
Support for relationship name in "foreign key", "column foreign key"  and “attribute relation” templates.
Object names administration – possibility to lock object name thus preventing any further modification.

Physical Model

Support for IBM DB2/UDB 9 and MS SQL Server 2008.
Support EDITIONING option on views, and support for invisible indexes in Oracle 11g physical model.


Dynamic reports – part of search functionality, search result can be filtered by object type and report can be generated for objects in result set.
Templates can be defined (including column names and sort order), replacement for boolean values is provided.
Supported report formats – HTML, PDF and RTF.
“Used in diagrams” section is added to reports for entities and tables – diagrams where entity/table is used are included into report.
Report can be generated for set of subviews and objects used in them, objects can be excluded from generated report. Report configuration can be saved and used later to generate report for the same set of objects.


Global search – regular expressions (optional) can be used to search any information entered into loaded designs and models including physical models.
Search at model level (including physical models) with simple and advanced mode – search for relational model also cover open physical models belonging to that relational model.
Part of search functionality, search result can be filtered by object type and dynamic report can be generated for objects in result set. Report templates for dynamic reports can be created.
Setting of common properties – part of search functionality, search result can be filtered by object type and common properties can be set for objects in result set.
Export to excel file and update model with previously exported excel file - export is integrated into dynamic reports functionality - XLS and XLSX type of reports. Exported file can be edited and changes applied to the same model. A log is generated for applied changes.

Transformation Scripts Better text editor with syntax highlight and code folding.
Debugging of JavaScript scripts using Rhino debugger.