Chat now with support
Chat with Support

Toad Data Modeler 7.0 - 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 MySQL 8.0 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

Refactoring Utility

Toad Data Modeler provides you with a tool that is able to refactor all references to an object when you change its name. For example, let's say you've changed name of an entity. Usually, you would have to go through the rest of the model and change the name in all the places where it is referenced. Refactoring Utility is able to do this automatically, saving your time.

Note: The utility refactors text properties only (e.g. AfterScript, BeforeScript, SQL tab, text Views...)

To open Refactoring Utility

  • Click Tools | Refactoring Utility

Renamed Objects

In section Previously Renamed Objectst (top-right), you can find objects that were renamed.

Use checkboxes to select what items you wish to use for current refactoring action.

Renamed objects will stay in section Previously Renamed Objects until you change names in other objects or until you enable icon in column Forget and click the Forget Selected Items button. (In this sample it should be used for EntityA).

Objects to Modify

In section Objects to Modify, you can find objects and properties that contain old names.

Current and Modified Code Previews

In section Current Code, the body of SQL code is shown. Use buttons Previous Term and Next Term to navigate among names in the same code.

Section Preview of Modified Code displays a preview of refactored code. Click any of the highlighted names and select old or new name or use the icons in middle column to reject suggested changes.

Note: Renaming from the default name (Entity1, Entity2...) is ignored deliberately.

Schema/Owner/Database Assignment

This tool allows you to assign or remove schema/owner/database to/from multiple object groups in your model at once.

To assign a schema/owner to your model

Select Tools | Schema/Owner Assignment.

Option Description

Select Schema/Owner/Database

Contains existing Schemas/Owners/Users in your model.

Select --None-- from the list to remove the existing schema from objects you mark in the Select types of objects section.

Assign to objects where value is not defined

Assigns schema/owner to objects, which have none assigned yet.

Confirm before assignment checkbox

Confirmation dialog for each object where schema is being assigned/removed will be displayed.

Select types of objects area

Mark objects which should be assigned a Schema/Owner.

Infer Relationships

This feature tries to map Primary Keys or Alternate Keys to identically named attributes in other entities.

Conditions:

  • Mapping is performed between key and non-key attributes. In other words, if identically named attributes are part of primary key in various tables, e.g. ID column in table Customer and ID column in table Order, the two ID columns will not be mapped and no relationship will be created.
  • Names must be identical and data type must be the same, including parameters.
  • Non-identifying relationships are created by default. In case you need an identifying relationship, edit the automatically added relationship and change its type to identifying manually.

To run the Infer Relationship function

Select Tools | Infer Relationship.

Note: Relationships created this way will be marked with a To-Do task prompting you to check whether the relationship has been created correctly.

Example:

Model with no relationships. See the Customer ID column in tables Customer and Order Record.
In table Film there is an alternate key with two columns Title and Director. Identically named columns are in table Customer Rating.

Run the Infer Relationship function and see the result:

Infer Relationships and Reverse Engineering

The same tool can be used automatically during reverse engineering.

Create a new connection or edit an existing stored connection and check the Infer Relationships checkbox to activate this feature.

Version Control

Related Documents