Oracle SQL Developer Data Modeler 3.1 Early Adopter


New Features


December 2011

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

Below is the list of general new features. For a list of all current product features see Data Modeler Feature List

Connections

Equivalent functionality as SQL Developer
JDBC-ODBC bridge can be used as native driver for supported databases
JTDS 1.2 driver (the one used in SQL Developer) can be used to import from MS SQL server in addition to native drivers from Microsoft

Database Native Types

Allow a list of supported native database types to be extended - PL/SQL data types or types like  LCR$_ROW_RECORD can be added through this functionality

Data Types

Added support for varchar(max) data type in MS SQL Server, CLOB logical type is mapped to varchar(max)  for MS SQL Server 2005

Diagrams

Relational - Option to show Primary Key, Unique Key and Foreign Key columns only
Option to show Labels in Transformation diagram
Default colors and fonts for "Legend" object can be set in preferences
Option in Legend properties dialog to show/hide Legend attributes

Domains Administration

Add a design level domain to a current open design

Impact Analysis

Functionality "Create Subview with Neighbors" in context menu for table in browser

Import and Export

Management of overlapping and folded foreign keys at entity level in Entity dialog. - used in engineering to relational model

Logical Model

Import using third party JDBC drivers - view definition will be imported if database supports INFORMATION_SCHEMA.VIEWS view

National Language Support

Language support is the same as SQL Developer and has been translated into French, German, Italian, Spanish, Brazilian Portuguese, Japanese, Korean,Simplified Chinese,Traditional Chinese

Performance

Improvements in loading and closing of large designs

Physical Model

Grants for Packages, Functions, Directories, Types, Collections and External tables
Grants at column level
Setting grants on more than one object
Improved support for XMLTYPE tables and columns

Preferences

The settings.xml file used to store preferences is no longer used. Preferences still can be imported from the existing settings.xml file.

Reports

Reporting templates can be defined - template defines which of the report sections are to be included in the generated report
Report for objects belonging to specific  subview - in addition to report for single table/entity or the whole model
Reports in PDF, HTML and RTF formats
Table of contents (TOC) for PDF and HTML format; RTF report is TOC ready (MS Word)
New reports added - structured, collection and distinct types, change requests and measurements

Reporting Repository

Additional support for:
-indexes can be disabled and enabled
-multidimensional model
-business info model
-change requests and measurements

Synchronization

Synchronization between model and data dictionary:
-list of values/ranges can be extracted from column check constraint
-one click synchronization in both directions
-support for several connections
-option to exclude tracking of column order when tables are compared - no need to recreate table as alter statements are generated

Versioning

Version history at design and system types level
Lock and unlock at design, model and subview level - applied for all objects in processed element
Support for branching and merging including:
- delayed resolution of merge conflict
- tree conflicts are detected in advance and functionality is provided for their resolution before merging to occur

Views

Comments can be set on view columns
Query Builder with support for:
- possibility to convert between ANSI and Oracle joins
- using graphical interface for building complex queries
- with persisting of layout of diagrams
- include/exclude schema name from defined query
- can work using only objects belonging to specific subview - for large models
- show SQL for current diagram only - in case of complex query built using several diagrams
Synchronization of changes in the model with already created views
Validation of view definitions created with previous version of Data Modeler