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

Simple Model Merge

Features and Tools > Model Actions > Merge Models > Simple Model Merge

This feature allows you to merge two physical models very quickly. However, in comparison to the model merge in the Sync & Convert Wizard:

  • You cannot select particular items for the model merge (e.g. not to merge particular entity). You can select only Object Types and Properties for the model merge.
  • The target model will always be overwritten.

To use the Simple Model Merge feature

  1. Open both models that you want to merge.
  2. Make the modified (updated) model active in the Application Window (source model).
  3. Select File |Synchronization | Simple Model Merge.
  4. From the To Model box, select a model that you want to update (target model). - This model will be overwritten.
  5. See other options.
Option Description

To Model

Select a target model.

More>>

Click this button to see and modify Object Types and Properties for the model merge.Object Types and Properties - OTPs

Close after Merge

Closes the Merge dialog after the process is finished.

Merge

Executes the process of model merge.

Close

Closes the Merge dialog.

  1. Click Merge.

Model Conversion

Data Type Conversion Settings

Features and Tools > Model Actions > Model Conversion > Data Type Conversion Settings

Before you start the conversion process, you can set conversion settings for data types.

  1. Enable Expert mode: Select Settings | Options | General | check the Expert Mode checkbox.
  2. From the main menu, select Expert Mode | Expert Mode Settings | Data Type Conversion Settings.

  1. In the Source and Destination boxes choose the desired databases.
  2. Press to display available data types. Click to view only exceptions.

You can see a list of data types of source model that will be converted to data types in destination model.

Example: Oracle Blob data type will be converted to Microsoft SQL Server 2012 model as Image data type. You can change the destination model data type.

Note: The modified database conversion settings are saved to DataTypeConversion.txn file stored by default in: C:\Users\*username*\AppData\Roaming\Quest Software\Toad Data Modeler\*Installation name*\Configs. If you want to restore the original conversion settings, you can simply delete this .txn file.

  1. Confirm OK.

Execute Script

If you want to use your own script for data type conversion, click the Go to Exception Script button. A dialog offer you to create a new script. Confirm and the newly created script will be shown in Script Editor, where you can edit it as you like.

Example:

function Convert(){

  var Log = System.CreateObject('Log');

  Log.Information('Konverze');

  Log.Information('Input MD: '+ InputModelDef.Abbrev );

  Log.Information('Output MD: '+ OutputModelDef.Abbrev );

  

  Log.Information(InputDataType.ConversionID.Code);

         

  var outDT                                     

  if (InputDataType.ConversionID.Code == 'C_X'){

   Log.Information('HERE');

    for( i = 0; i < OutputDataTypes.Count; i++ )

    {

      outDT = OutputDataTypes.GetObject( i );

      Log.Information( outDT.Name );

      if (outDT.Name=='Box') {

        return(i);

      }

    }

  }  

  

  return(0);

}

PER - PER Conversion Information

Features and Tools > Model Actions > Model Conversion > PER - PER Conversion Information

See some basic information on what is converted and how during the PER to PER conversion.

  • Data Types are converted.
  • Permissions are compared by names.
  • SQL code is copied and commented not to generate any code.

See other details here:

Item to Convert

Model A

(Source Model)

Model B

(Destination Model)

Result

Data Types

 

Supported data type

Supported data type

Same data type

Example*:

Integer

Integer

Integer

 

Supported data type

Equivalent data type

Equivalent data type

Example**:  

Float

Real

Real

Permissions

 

Supported Permission

Supported Permission

Same Permission

Example:

SELECT

SELECT

SELECT

 

Supported Permission

Unsupported Permission

--None--

Example:

DROP (MySQL 5)

--None-- (Microsoft SQL 2005)

--None-- (Microsoft SQL 2005)

 

Unsupported Permission

Supported Permission

Model B Permission

Example:

--None-- (Microsoft SQL 2005)

DROP (MySQL 5)

DROP (MySQL 5)

(DROP preserved in already existing model.)

Deny Permission

 

Deny Permission Supported

Deny Permission Supported

Deny Permission Converted

 

Deny Permission Supported

Deny Permission Unsupported

--None--

 

 

Deny Permission Unsupported

Deny Permission Supported

Model B Deny Permission

Example:

MySQL 5

Microsoft SQL 2005

Microsoft SQL 2005 (Deny permission preserved in already existing model.)

Grantor

 

Grantor Supported

Grantor Supported

Grantor Converted

 

Grantor Supported

 

Grantor Unsupported

 

--None--

 

 

Grantor Unsupported

 

Grantor Supported

 

Grantor is empty.

Example:

MySQL 5

 

Microsoft SQL 2005

 

Microsoft SQL 2005 (Grantor preserved in already existing model.)

Users and User Groups

 

Supported

Supported

Converted successfully

 

Supported

Unsupported

--None--

 

Unsupported

Supported

--None--

Example:

Users unsupported in PostgreSQL

Users supported in Microsoft SQL 2005

--None--

Model A - Currently opened model that you want to convert.

Model B - Model to which you want to convert Model A.

Complete Model A is converted to Model B.

Other Information

  • Conversion between PostgreSQL and Microsoft SQL: Serial and BigSerial data types in PostgreSQL are converted to Identity in Microsoft SQL. Identity in Microsoft SQL is converted to combination of sequence and default "nextval" in PostgreSQL. 
  • Conversion between PostgreSQL and MySQL: Serial data type in PostgreSQL is converted to Autoincrement in MySQL. Autoincrement in MySQL is converted to combination of sequence and default "nextval" in PostgreSQL.
  • Conversion between PostgreSQL and Oracle: Serial and BigSerial data types in PostgreSQL are converted to combination of sequence and a sequence selected for attribute in Oracle. A sequence selected for attribute in Oracle is converted to default "nextval" in PostgreSQL (the sequence is converted automatically).
  • Conversion from Oracle to Microsoft SQL (and Microsoft SQL to Oracle): Automatic conversion of Identity in Microsoft SQL to Sequence in Oracle (and back).
  • Conversion from Oracle to MySQL (and back): Sequence in Oracle are converted to Autoincrement in MySQL (and back).
  • Conversion from Microsoft SQL to MySQL (and back): During conversion of Identity (Microsoft SQL) to Autoincrement (MySQL) and back the new IdentitySeed/Initial Autoincrement is taken into consideration. (In version 3.4, only conversion between checkbox Identity and Autoincrement was possible.)
  • Model Conversion from MySQL to Microsoft SQL and Oracle: MySQL Enum data type is converted to Char data type, a check constraint for the attribute is created, the parameter is preserved (see the SQL tab of the Check Constraint Properties dialog).

* Data types conversion examples - conversion from MySQL 5 model to SQL Server 2005 model.

** See the equivalent data types for conversion in the Settings menu | Data Type Conversion Settings.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating