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 Generation

Databases > Microsoft SQL Server 2008 > Script Generation
 

 

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 2012

Reverse Engineering

Databases > Microsoft SQL Server 2012 > Reverse Engineering

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

Note:

  • 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*/.

Specifics

Databases > Microsoft SQL Server 2012 > Specifics

Entity

Fulltext Index Tab

Fulltext Index tab, new combo box Search Property List.

SearchPropertyList object has only listing function. It is not possible to define it (CREATE/DROP/ALTER not supported).

Index

Type of Index box - new Columnstore index type.

For Columnstore indexes, many options are available, though they are not valid and they do not get generated.

Spatial Index Parameters Tab

New Spatial Tessalation Scheme box with new options GEOMETRY_AUTO_GRID and GEOGRAPHY_AUTO_GRID. Based on selection, further Bounding Box and Grids options are enabled or disabled.

Cells Per Object— Default value changed to empty from 16.

Trigger

With Append option is not available now and the checkbox was removed from trigger.

File Table

New File Table object is available.

  • Keys can be defined in text on tab Keys (ALTER TABLE tablename ADD UNIQUE (attr)).
  • Indexes can be defined in text on tab Indexes (CREATE INDEX ...).
  • Triggers can be defined in text on tab Triggers (CREATE TRIGGER ...).
  • Permissions can be defined in text on tab Permissions (GRANT ...).
  • Comments can be defined on tab Description.
  • In case the user wants to define checkconstraints in text, the After Script tab can be used.
  • In case the user wants to define foreign keys in text, the After Script tab can be used.

Sequence

Define Data Type in Data Type for Sequence Valuebox.

Available data types: tinyint, smallint, int, bigint, decimal and numeric with a scale of 0. You can use also any user-defined data type (alias type) that is based on one of the allowed types.

Extended Properties

Extended Properties are supported for the following objects (generally where comments are supported):

  1. Objects with new tab Extended Properties.
  2. Objects for which Extended Properties are loaded during reverse engineering as a text as for example After Script, function parameters, procedure parameters, view columns, key/index/foreign key for Filetable.

Other objects in Model Explorer:

  • Sequence
  • Search Property List
  • FileTable
  • Filegroups
  • Partition Schemes
  • FilestreamFilegroups - Similarly to Filegroups, FilestreamFilegroups work in Toad Data Modeler only as a list. During script generation, the FilestreamFilegroups definition is not generated and during reverse engineering  the definition is not loaded either (only names are loaded).
  • Stoplists - Similarly to Filegroups, Stoplists work in Toad Data Modeler only as a list. During script generation, the Stoplist definition is not generated and during reverse engineering  the definition is not loaded either (only names are loaded).
  • Partition Functions
  • Fulltext Catalogs
  • XML Schema Collections
  • Assemblies
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating