Chat now with support
Chat with Support

Toad Data Modeler 6.5 - User Guide

Introduction User Interface Models and Model Objects
Physical Data Model
Entity Relationship Diagram Objects Basic Database Design Advanced Database Design
Universal Data Model Logical Data Model Working with Model Objects
Features and Tools
Application Variables Export/Import DDL Script Generation Graphics Model Actions Print Create New Project Reports Reverse Engineering Scripting and Customization About Templates Tips and Tricks Toad for Oracle Integration Toad Intelligence Central (TIC) Integration Tools Version Control
Options and Configuration Databases
Amazon Redshift 1.0 IBM DB2 LUW 9.5 IBM DB2 LUW 9.7 IBM DB2 LUW 10.1 IBM DB2 LUW 10.5 IBM DB2 LUW 11.1 IBM DB2 z/OS 10 IBM DB2 z/OS 11 Greenplum 4.1 Greenplum 4.2 Ingres 9.3 Ingres 10.0 EDB Postgres Advanced Server 10 Microsoft Access 2007/2010 Microsoft Azure SQL Database V12 Microsoft SQL Server 2005 Microsoft SQL Server 2008 Microsoft SQL Server 2012 Microsoft SQL Server 2014 Microsoft SQL Server 2016 Microsoft SQL Server 2017 MySQL 5.0 MySQL 5.1 MySQL 5.5 MySQL 5.6 MySQL 5.7 Oracle 10g Oracle 11g Release 1 Oracle 11g Release 2 Oracle 12c Release 1 Oracle 12c Release 2 Oracle 18c Specifics - Oracle 12c Release 2 PostgreSQL 9.0 PostgreSQL 9.1 PostgreSQL 9.2 PostgreSQL 9.3 PostgreSQL 9.4 PostgreSQL 9.5 PostgreSQL 10 SQLite 3.7 Sybase ASE 15.5 Sybase ASE 15.7 SAP ASE 16.0 Sybase IQ 15.2 Sybase SQL Anywhere 11 SAP SQL Anywhere 17 Teradata 13 Vertica Database 8.0
Copyright Legal Notices

Parent Attributes

You can change the attribute name e. g. in the following cases:

  • When you create a self-relationship.
  • Whenever you want to change a Foreign Key attribute name.


You have just added a self-relationship to the Film entity.

  1. A copy of your identifying key attribute has been created in the entity - Film ID. Now you have two Film ID attributes in the Film entity.

  1. Edit the newly created Film ID attribute, define a new Name . The link to parent attribute is displayed on top right-hand corner of the form.

  1. Confirm OK and see the change on the Workspace.

Advanced Database Design

Toad Data Modeler allows you to design Entity Relationship Diagrams of specific database platforms, convert physical model from one database platform to another, create an ER Diagram directly from your database (Reverse Engineering feature), update physical models, generate DDL/SQL scripts and Change Scripts, create Dictionary Types, Views, Triggers, Functions, generate detailed documentation to your model (in HTML, RTF, PDF, XSLT formats) and much more.

This chapter describes features and functions related to Physical Data Modeling. Look around each section to get the information you need.

Note: See the sample physical model Videorental (Oracle 10g db) that is included in the installation package of Toad Data Modeler. Default location is: C:\Program Files (x86)\Quest Software\Toad Data Modeler6.5.6\Samples.

Benefits of Physical Data Model

  • Detailed definition of database structure, including database specific items, for example:
    • Stored procedures
    • Functions
    • Triggers
    • Views
    • Materialized views
    • Sequences (auto increments) etc.
  • Possibility to synchronize local model with existing database.
  • Possibility to specify logical names for objects (captions for tables, attributes and other objects).
  • Detailed database specific information can be exported to HTML/RTF/PDF or XML/XHTML/CSV reports.
  • Automatic generation of SQL code for selected objects (SQL code generation is not available in Logical and Universal Model)
  • Automatic migration of PK attributes to child entities (Attributes don't migrate to child entities in Logical Model)

About Advanced Options

Toad Data Modeler supports several database systems. As there are differences among databases, there are only applicable to specific databases.

For example:

  • Microsoft SQL Server 2000 and higher only support Dictionary Types, which are called User-Defined Data Types in database itself
  • PostgreSQL databases do not support Users, only User Groups. Instead of Users, Roles are used for managing permissions.
  • and others...

Database platform and version specific information are listed in the respective topics in the Databases chapter.

Alternate Keys

You can create a relationship between a Parent and Child entities using:

  • Key (Primary or Alternate Key) of parent entity
  • Unique Index of parent entity

Alternate keys are used when you want to link two entities using two attributes. These two attributes make one unique item.


You would like to create a composite alternate key which contains Title and Director attributes in the Film entity.


  1. Edit the Film entity.
  2. In the Entity Properties form click the Keys tab. Here, primary keys and alternate keys are stored, and you can manage them easily using the Add, Edit and Delete buttons. Now click Add to create a new key and confirm by clicking Apply.
  3. Edit the new key.
  4. Define its properties on tab General and then switch to the Attributes tab.
  1. From the window Available, select attributes Title and Director and click the Add arrow button to move them to the Selected window.
  2. Set properties in other tabs as you wish (e.g. Notes) and confirm.


Scenario: After creating the alternate key, you would like to use it for linking entities.

To select the alternate key for relationship

  1. Double-click the relationship.
  2. From the Parent Key box, select the alternate composite key title-director.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating