Chat now with support
Chat with Support

Toad Data Modeler 6.2 - User Guide

Introduction User Interface Models and Model Objects
Physical Data Model
About Physical Data Modeling Benefits of Physical Data Model Entity Relationship Diagram Objects Basic Database Design Advanced Database Design
Universal Data Model Logical Data Model Working with Model Objects Model Properties Model Statistics
Features and Tools
Application Variables Export/Import DDL Script Generation Graphics Model Actions Print Projects Reports Reverse Engineering Scripting and Customization SQL Templates Tips and Tricks Toad for Oracle Integration Toad Intelligence Central (TIC) Integration Tools Version Control
Options and Configuration Databases
Supported Databases Connection Types by Database DB2 UDB v. 8 (LUW) DB2 v. 9 (LUW) DB2 v. 9.5 (LUW) DB2 v. 9.7 (LUW) DB2 v. 10.1 (LUW) DB2 v. 10.5 (LUW) DB2 z/OS v. 9 DB2 z/OS v.10 DB2 z/OS v. 11 Greenplum 4.1 Greenplum 4.2 Ingres 9.3 Ingres 10.0 Microsoft Access 2000/2002/2003 Microsoft Access 2007/2010 Microsoft Azure SQL Database Microsoft Azure SQL Database V12 Microsoft SQL Server 2000 Microsoft SQL Server 2005 Microsoft SQL Server 2008 Microsoft SQL Server 2012 Microsoft SQL Server 2014 Microsoft SQL Server 2016 MySQL 5.0 MySQL 5.1 MySQL 5.5 MySQL 5.6 MySQL 5.7 Oracle 9i Oracle 10g Oracle 11g Release 1 Oracle 11g Release 2 Oracle 12c Release 1 Oracle 12c Release 2 PostgreSQL 8.1 PostgreSQL 8.2 PostgreSQL 8.3 PostgreSQL 8.4 PostgreSQL 9.0 PostgreSQL 9.1 PostgreSQL 9.2 PostgreSQL 9.3 PostgreSQL 9.4 PostgreSQL 9.5 SQLite 3.7 Sybase ASE 12.5 Sybase ASE 15 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
Legal Information

Export/Import Dictionary

Models and Model Objects > Physical Data Model > Entity Relationship Diagram Objects > Export/Import Dictionary

Toad Data Modeler allows you to use dictionary items also in other models. You can simply export all of them to the .TXI file, and then import them to any model at any time. You can save the .TXI file where you want, no default path is defined.

Dictionary items are:

  • User Data Types
  • Dictionary Types
  • Domains

Domains

They have only a logical meaning. They are not generated in DDL/SQL script. If a domain is used in attribute, only values of the domain are transferred to the attribute during the DDL script generation process.

User Data Types

They are data types defined by users and can be generated in final DDL script.  User data types are not derived from data types.

Dictionary Types

They are data types that are derived from other data types.  They can be generated in final DDL script.

 

How to Export/Import Dictionary

You want to use dictionary items of Model A in Model B:

  1. Open Model A.
  2. Select Model | Export Dictionary.
  3. Save the .txi file.
  4. Open Model B.
  5. Select Model | Import Dictionary.
  6. Select the .txi file and click Open.

Note:

  • Domain Check Constraints are imported/exported too.
  • It's not possible to make selection of the dictionary items for the import/export. All the dictionary items are always imported/exported at one jump.

Relationships

Notation and Cardinality

Models and Model Objects > Physical Data Model > Basic Database Design > Notation and Cardinality

IE Notation

 

Cardinality

One-to-many relationship is represented by this symbol:

One-to-one relationship is represented by this symbol:

 

Parent: mandatory Child: mandatory

Parent: mandatory Child: optional

Parent: optional Child: mandatory

Parent: optional Child: optional

 

IDF1X Notation

 

Cardinality

,  ,   zero, one or more

one or more

zero or one

 

Parent: mandatory Child: mandatory

Parent: mandatory Child: optional

Parent: optional Child: mandatory

Parent: optional Child: optional

See Synchronization of Not Null and Mandatory Parent for more information.

Relationship Types

Identifying Relationship

Non-identifying Relationship

Non-identifying Self-relationship

M:N Relationship

Relationship Types

Models and Model Objects > Physical Data Model > Entity Relationship Diagram Objects > Relationship Types

Toad Data Modeler supports the following relationship types (physical model):

  • Identifying
  • Non-identifying
  • Self-relationship for non-identifying relationship
  • M:N relationship
 

Identifying Relationship

Primary key migrates from parent entity to child entity and there becomes a part of the primary key. It is used when the primary key of the child entity is unable to provide definite identification.

An entity, connected with a parent entity through an identifying relationship, is called "dependent" entity and is shown in a model with rounded corners.

The Order Record entity cannot exist itself. It is dependent on entities Customer and Film. Therefore the Identifying relationship is used. The Order Record entity is a dependent entity, and the Customer ID and Movie ID items are its unique record identifiers.

 

Non-Identifying Relationship

Primary key migrates from parent entity to child entity and does not become a part of the primary key. Non-identifying relationships are represented by dashed lines. In the dependent table, the attribute is referred to as a foreign key.

The Film ID as the unique identifier for Film is sufficient. Therefore the non-identifying relationship is used. The Genre ID is only a foreign key. The film can exist without being assigned to a genre, therefore the Film entity is an Independent entity.

 

Self-Relationship for Non-identifying Relationship

 

M:N Relationship

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating