Oracle SQL Developer Data Modeler is a 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.
Oracle SQL Developer Data Modeler provides a model driven approach for database design and generation, implemented by integrated set of models - Logical, Data types, Dimensional, Relational, Data Flow diagrams and Physical models for supported Oracle Databases, Microsoft SQL Server 2000 and 2005, IBM DB2/390 and DB2 LUW V7 and V8 representing different aspects or level of details and vendor specifics of the modeled information system.
Get Oracle SQL Developer Data Modeler and take it for a test drive to see what it's all about!
NOTE:
You need to create an Oracle account in order to access the downloads.
Here are some key features of "Oracle SQL Developer Data Modeler":
· Logical Models
· Subject Area Management
· Impact Analysis
· DataTypes Models
· Naming Standards
· Relational Models
· Design Rules
· Dimensional Models
· Importing
· Data Flow Diagrams Reporting
· Physical Models (Database specific)
· Integrated Version Support
· Domains
· Wizards
What's New in This Release: [ read full changelog ]
Accessibility:
· improving accessibility within the product is an ongoing process.
DDL:
· check constraint is generated without constraint itself
· ddl generation window empty if using automatic index generation for foreign keys
· sequences and triggers for auto increment columns are not generated in compare
· compare models without recreation of tables for changed datatype
· db2/390 8: ddl generation does not take into account index property partitioned
· invalid ddl for statement level trigger
· ddl script for a primary key using index sort doesn't work
Diagram:
· cannot delete table/entity presentation from diagram (subview)
· pk dialog shows error when invoked from browser
Import and export:
· import ddl - order of pk columns is wrong, cannot get compos. Fk
· index colums with sort order = desc is captured as index expression
· objects lost in physical model in compare/merge models - sequences, triggers
· easy sync - no second chance to enter correct password
· click "synchronize model...
Find us on Google+
