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

Script Generating

Databases > Microsoft SQL Server 2014 > Script Generating


Note: To generate the table, column descriptions for SQL Server db in Toad Data Modeler, schema/owner has to be defined. Please see the Entity Properties form | General tab and from the Schema box select a schema or click the icon on the right to open the Schema dialog and define a new schema, then select it for the entity.

Microsoft SQL Server 2016

Reverse Engineering

Databases > Microsoft SQL Server 2016 > Reverse Engineering

See Reverse Engineering - Microsoft SQL Server 2000 for more information.


  • To load Data Compression defined in index during reverse engineering, it is necessary to select the Load Index Options  checkbox (it is selected by default) on page Options.
  • Load Permissions - Only permissions to views, tables, columns and functions are loaded during reverse engineering. Permissions to users, schemas and user groups are not loaded (they can be only generated in SQL script.)
  • Comments on views and their columns are reversed. Comments on views are stored in the View Properties dialog | Description tab. Comments on view columns are loaded to View Properties dialog  | After Script tab (if you want to create them during model creation, you need to enter them manually - and in this form: --comment and/or /*comment*/.


Databases > Microsoft SQL Server 2016 > Specifics

External Table support (PolyBase external table that references data stored in Hadoop cluster or Azure blob storage). External Tables can be found in Physical Model Explorer.

Security Policy support (for row-level security). Security Policies can be found in Physical Model Explorer.

New model objects with simplified support:

  • Column Encryption Key - currently without any properties, used for Encrypting Columns.
  • External Data Source - currently without any properties, used for External Table.
  • External File Format - currently without any properties, used for External Table.

IF EXISTS support for DROP commands of certain object types:

  • Entity, View, Relation, Trigger (entity/view), Key, Index, Default, Rule, DictType, UDT, Procedure, Function, Aggregate (Functions), Synonym, Assembly, Sequence, FileTable

  • To use the clause, enable the Check Object Existence Before Processing Drop Commands option in DDL Script Generation | Detail Settings.


  • Memory Optimized Tables:
    • It is now possible to create the following objects in memory optimized tables:
      • Triggers (Natively Compiled only)
      • Index (Clustered Columnstore only)
      • Foreign Key constraints (between memory optimized Tables)
      • Check constraints
      • Unique constraints
  • "Period for System_Time" and "System-Versioned Temporal Table" support for Tables (Attribute Properties | Temporal Properties tab AND Entity Properties | Temporal Table Properties tab)


  • Dynamic Data Masking support for Attributes (Attribute Properties | Masking and Encryption tab | Dynamic Data Masking)
  • Always Encrypted support for Attributes (Attribute Properties | Masking and Encryption tab | Encrypting Columns)


  • New Function types:
    • Natively Compiled Scalar Function
    • Natively Compiled Inline Table-valued Function
  • EXECUTE AS CALLER for Natively Compiled Stored Procedure Functions (used by default).


  • New parameter - COMPRESSION DELAY for COLUMNSTORE Indexes.

  • Filter predicates (WHERE) can be now used in non-clustered COLUMNSTORE Indexes.
  • Non-clustered Indexes can be now created even when CLUSTERED COLUMNSTORE Indexes already exist.


  • ALLOW_ENCRYPTED_VALUE_MODIFICATIONS = ON | OFF support for Users (in Reverse Engineering).


  • Support for Stretch Database (REMOTE_DATA_ARCHIVE) in SQL Server 2016
  • To create a Table for remote data archive see Entity Properties | Stretch Database Properties

NOTE: REMOTE_DATA_ARCHIVE is not supported for Memory Optimized Tables.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating