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 > Oracle 12c Release 2 > Script Generation

Specifics

Databases > Oracle 12c Release 2 > Specifics
  • Options are available in Options | Model | Physical Model | Oracle | Oracle 12c Release 2
  • Identifiers now can be 128 characters long (exception - Tablespaces)

Support for Collation

  • New property COLLATION can now be used for tables (column collation), views, materialized views, users, packages, procedures, functions and types
  • List of Collations displays objects

Tables

Table Properties and Physical Properties Tab

The following properties’ definitions needs to be entered manually into the text field and is loaded automatically during Reverse Engineering:

  • FOR SERVICE property of INMEMORY tables - can be defined for the whole tables, for their partitions and subpartitions
  • Inmemory_column_clause for NO INMEMORY tables - you now can specify it to enable or disable specific table columns for the IM column store, and specify the data compression method for specific columns
  • READ ONLY or READ WRITE property - can be defined for the whole tables, for their partitions and subpartitions
  • New In-Memory Column Store policy
  • Compression policy - new option COLUMN STORE COMPRESS FOR QUERY ROW AFTER ilm_time_period OF NO MODIFICATION
  • New properties COMPRESSION and INDEXING can be used for subpartition templates
  • Automatic list partitions can now be used for partitions
  • Multi-Column List Partitioning can now be used for partitions and subpartitions
  • List of value lists can be specified for multi-column list partitions

External Tables

  • Now you can use NOT NULL, UNIQUE, PRIMARY KEY, FOREIGN KEY constraints for external tables
  • Can use ENCRYPT property, Virtual Column, range/list partitions and subpartitions
  • Do not have to use DEFAULT and LOCATION in their definitions

Misc.

  • New Encrypt Algorithms are used for columns

Indexes

Index Properties Tab

The following property definition needs to be entered manually into the text field and is loaded automatically during Reverse Engineering:

  • New Compress parameters COMPRESS ADVANCED and COMPRESS ADVANCED HIGH - can be defined for an index and its individual partitions (global and local)

Misc.

  • New option DEFERRED INVALIDATION is available. Default is IMMEDIATE INVALIDATION

  • Column COLLATION is recognized during Reverse Engineering

Keys

Using Index Properties Tab

The following property definition needs to be entered manually into the text field and is loaded automatically during Reverse Engineering:

  • New Compress parameters COMPRESS ADVANCED and COMPRESS ADVANCED HIGH

Materialized Views

  • New property FOR SERVICE - can be defined for the whole tables, for their partitions and subpartitions; the definition needs to be entered manually into the text field (Physical Properties Tab) and is loaded automatically during Reverse Engineering:
  • New Encrypt Algorithms - can be set in the Column Aliases field
  • New ON STATEMENT mode:
    • Refresh type needs to be FAST
    • The materialized view’s defining query needs to include the ROWID column of the fact table.
    • ON STATEMENT mode cannot be converted to a different mode using ALTER MATERIALIZED VIEW but instead DROP/CREATE is performed during Change Script Generation

  • New property ENABLE ON QUERY COMPUTATION - by default: DISABLE ON QUERY COMPUTATION
    • If enabled, the refresh mode COMMIT cannot be used

User

The following properties’ definitions need to be entered manually into the text field (as CREATE USER sentence) and are loaded automatically during Reverse Engineering:

  • New property HTTP DIGEST ENABLE
  • New property LOCAL TEMPORARY TABLESPACE

PostgreSQL 8.1

Reverse Engineering

Databases > PostgreSQL 8.1 > Reverse Engineering

Available Data Providers are:

  • Native Connection

Native Connection:

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating