Chat now with support
Chat with Support

Toad Data Modeler 6.3 - 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

Application Variables

Features and Tools > Application Variables > Application Variables

In Toad Data Modeler you can use application variables in:

  • Names/captions in Physical Model Explorer and Designer - use the percent button () to enter the selected variable in the current cursor location
  • DDL Script and Change Script Generators
  • Report Generation - Check Resolve Application Variables in Report Wizard | Options
  • Default Values (e.g. relationship names) - Select Settings | Default Values to adjust default values for objects
  • About Templates
  • Certain properties (most notable ones are SQL, Before Script, After Script)

Note: To see where you can use application variables, see Expert Mode Menu | Reference Guide. If a property has Resolve Application Variables attribute, you can use application variables within it (e.g. PEREntity - BeforeScript).

Application variables are usually resolved during SQL script generation.

Accessing Application Variables

Application variables can be easily accessed via the which can be found in object properties forms. When you click it, the Application Variable dialog opens and displays available variables and in which properties they are supported.

Syntax of Application Variables

  1. <%ApplicationVariableName%> - Example: <%Date%>
  2. <%<% ApplicationVariableName %>%> - Example: <%<%Date%>%>

Syntax 2) is useful in Templates and Default Values. Variables using this syntax will be resolved only during SQL Script/Report generation as opposed to variables with syntax 1) which are resolved immediately after creating an object.

Note: OwnerName, OwnerCaption - Explanation: E.g. For attribute it is an entity, for entity it is a model. It has nothing to do with object Owner/Schema.

Application Variables - Examples

Features and Tools > Application Variables > Application Variables - Examples

Application Variables and User Template

Application Variables and Default Values

Example: Define a new name and caption for relationships of your model.

Caption: <%ParentTableName%> - <%ChildTableName%>

Name: <%ParentTableName%>_<%ChildTableName%>

Application Variables and Self-Relationships

Possibility to define a name for propagated attributes in self-relationships (e.g. via prefix, suffix etc.)

Select Settings | Options | Physical Model | Self Relation Attribute Name/Caption.

Example: Name: FK_<%ParentAttributeName%>, Caption: Foreign <%ParentAttributeCaption%>

Application Variables and Text Properties

You can use some text properties of particular objects in a similar way as application variables.

Example: You want to see your comments in a pop-up window on the Workspace whenever you point your mouse cursor at the entity name. But comments are not displayed this way, only notes. OR You want to generate notes in SQL script.

Possible solution: In the Entity Properties form,

  1. On tab Notes, write the text, e.g. My Description.
  2. On tab Comments, write: <%Notes%>.
  3. Confirm Apply.
  4. See the SQL Preview tab.
  1. Click to display a quick help bar with application variables that are possible to use in entity.

Example: Name is property of entity. It is of widestring data type, so you can use application variable <%Name%>. Author is not property of entity. However, you can use the application variable <%Author%> in entity. - All the application variables that you can use for entity are available in the list.


  • Double-click the selected application variable to use it in the box/place where you have your cursor.
  • Press Esc to close the dialog.

Application Variables in Wizards

Sync & Convert Wizard| page Settings and Report Wizard | page Options and the Resolve Application Variables checkbox.

Uncheck the checkbox to compare models/generate report without resolving the application variables.

Check the checkbox to compare models/generate report while resolving the application variables.


Microsoft Excel

Features and Tools > Export/Import > Microsoft Excel

Toad Data Modeler allows you to export metadata to Microsoft Excel. Comments, notes and other properties can be modified and the file can be then imported back into Toad Data Modeler.

To export your model to a Microsoft Excel document

  1. Select File Menu | Export | Export to Excel.
  2. Select the entities and relationships you want to export.
  3. Click Export. A new Microsoft Excel document will be created in the specified destination.

To import the data back from a Microsoft Excel document

  1. Select File Menu | Import | Import from Excel.
  2. Locate the Excel document and click Open.
  3. Select which tables and relationships should be imported.

  4. Click Import. The existing model will be updated to reflect the changes made in the Excel document.

The following table illustrates the modified properties:

Modification Property type


Unlocked String









Boolean GenerateSQLOnly


Locked List





NOTE: Aliases of entities and attributes are in columns “From” or “Attributes” in a format: “Object AS alias” in an exported file

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating