1. Oracle SQL Developer Data Modeler
Emerson Borsato, PhD

2. About presenter Bachelor degree in Computer Science (1997)
Master Degree in Applied Informatics in Healthcare (2000)
Doctoral Degree in Medical Informatics (2005).
Worked with Intermountain Healthcare since with the Clinical Knowledge Repository and Authoring Tools design and development.
Areas of interest:
Web XML Authoring
Semantic Web
Java development

3. Agenda Objectives Oracle SQL Developer Data Modeler
Share knowledge with the audience
Find a “I didn’t know about that!”
Oracle SQL Developer Data Modeler
Approaches for data modeling
Developer’s types of approaches
Code centric approach
Data centric approach
Software development discussion

4. Introduction Diagrams are very efficient communication tool
Multiple models for different users
Logical Model - Data architects and users
Relational Model – developers
Physical model – database administrators
It also includes Data flow diagrams
It is a data-centric modeling tool
Personal experience with SQL Developer Data Modeler
Ref.: Oracle FAQs

5. Oracle SQL Developer Data Modeler About
Free, stand-alone
Full spectrum of data and database modeling tools and utilities
Entity Relationship Diagrams (ERD), Relational (database design), Data Type and Multi- dimensional modeling
Forward and reverse engineering and DDL code generation
Imports from and exports to many sources and targets
Connects to any supported Oracle Database
Is platform independent
The product was first released on July 1, 2009
Current version
Oracle SQL Developer Data Modeler 3 ( )
Available from OTN.
Java-based
Standalone
Multi database support
Multi platform support
Windows
Linux
Mac OS

6. Domains
Useful when creating types that should be consistent among other entities that share the same data
For instance Street name can be used in multiple tables.
Tools -> Domains Administration.
Available Domains: Available types – allow viewing and editing its properties
Allow users to define and reuse a data type with optional constraints or allowable values
Domains can be applied in the logical and relational models

7. Domains Are translated to the pertinent physical model Include Name
Logical Type
Size
Precision
Scale
Synonym
Comment
Check Constraint
Ranges
Value List

8. Data Types Model Support SQL99 (Object Relational Modeling)
user-defined composite
ability to add super-type and sub-types inheritance hierarchy
Definitions are mapped to Oracle object types in an Oracle physical model
Applied in logical and relational models
Generated in DDL

9. Logical Model Entity Relationship Diagram (ERD)
Entities, attributes, and relationships
Standard logical modeling facilities
Drawing entities and relationships, plus the following key features:
Box-in-box presentation for the super-type and sub- type hierarchy of entities
Support for exclusive relationships (arcs)
Barker or Bachman notation
Can be engineered from and to Relational model
Bachman notation
Barker notation

10. Relational Model Schema or database model
tables, columns, views, and constraints
Independent of the constraints of the target physical platform(s) – Database independent
Forward engineering from logical model resolves
Many-to-many
Supertype/sub-types
Name standardization

11. Physical Model Associated with a relational model
Defines the physical attributes
Database and version specific
Supports (most) Oracle physical objects
Exposes objects’ structure and definition in the object browser
One relational model can generate multiple physical models

12. Multidimensional Model
Multidimensional database (MDB)
optimized for data warehouse
online analytical processing (OLAP)
Multidimensional databases are created using input from existing relational databases
Oracle Sql Developer data modeler supports
Modeling of Cubes, Dimensions, Levels and Hierarchies, Measures and slices
Start from ROLAP, XMLA or from scratch
Generate Oracle Analytical Workspaces
More info:

13. Dataflow diagrams Shows the flow of data between process
It needs Logical Model with Entities and Attributes
Attributes are used to select data used in the information structures
Primitive Process
Independent of other process
It stands on its own
Composite Process
Process and its sub-processes
Transformation Process
Gets data from external sources and transform it before storing
Requires transformation tasks

14. Business Information
Is not added by browsing the Business information node
Added at the object or model level
Models, Entities, Attributes, Columns and Process

15. Forward/Reverse Engineering
Logical model to maps to one or more relational models
Each relational model maps to one logical model
Each relational model maps to one or more physical models
Each physical model maps to one relational model
Engineering options
General
Compare/copy
Synchronization
Include design glossary and naming standards

16. Import Metadata DB Connections File Oracle MS SQL Server IBM DB2
Generic JDBC
Oracle Designer repository
File
Other Modeling tools
CA ERwin
Multi-Dimensional
Cube views
XMLA

17. Inputs and outputs Reverse engineering
Importing from the Data Dictionary
Allow objects selection to be included in the import or reverse engineering process
Allow filtering out secondary tables
If selected, imports Oracle object types, VARRAYs, and nested table.
table, view, column, method parameter or result
Import from multiple schemas to a single diagram for all tables and views and a separate

18. Import

19. Script Generation
Generates DDL scripts for Oracle, DB2 and SQL Server,
Database specific
Cube Views Metadata or XMLA files for multi- dimensional models
XML files for Oracle OLAP or directly to create Oracle Analytical Workspace
Generating DDL and Self Managing Scripts
In addition to regular DDL scripts, SQL Developer Data Modeler generates advanced scripts
Offer self-managing functionality - “start and stop”
Can be restarted from the point (step) of failure.

20. Subversion integration
Connect to SVN through Versioning Navigator
Check in using import to subversion
Multiple users check out designs
Pending Changes dialog provides feedback to all users
Commit changes to repository
Manage conflicts

21. Modeling Approaches Top-Down Bottom-Up Targeted New database
Based on extracting metadata from an existing database or
using the DDL code obtained from an implementation of an existing database
Targeted
Adapting a database to new requirements

22. Items for thinking and discussion
Data base design is in many cases overlooked
Depending of the developer(s) style
In many cases developers want to create DB agnostic applications
As well application server agnostic
Some (perhaps most) software developers apply the use of ORM (ex. JPA)
Some code generators will even create the physical models and relationship (Grails)
When database structures go beyond the basics, programming frameworks are not prepared

23. SQL Data Modeler – Features summary
Logical Models
DataTypes Models
Relational Models
Dimensional Models
Data Flow Diagrams
Physical Models (Database specific)
Domains
Subject Area Management
Impact Analysis
Naming Standards
Design Rules
Importing
Reporting
Integrated Version Support
Preferences
Wizards

24. Discussion