Toad Data Modeler allows you to create models from DDL/SQL scripts. This feature is not supported in all database platforms and versions.
Creating models from DDL/SQL Scripts is very similar to creating models from physically existing databases. You need to define "Connection" to your SQL file and then you can either reverse engineer the database structure or open Object Explorer and add objects to existing model using the Drag and Drop technique (Live Reverse Engineering).
To manage database connections
To create a new SQL file Connection
To create a new model from saved DDL script Connection
Note: You may not see all object types, depending on your Connection settings. This can be changed by editing the Connection in Connections dialog and then checking appropriate objects in the What to Reverse dialog.
Toad Data Modeler allows you to reverse engineer a database structure of unsupported database platforms. Tables, columns, primary keys, indexes, relationships, procedures and views are loaded (depends on the database). Then it is necessary to convert the reversed model to a model of any supported databases.
To reverse an ANSI model
Follow the steps defined in topic Connections and in step Select Data Source, select Universal DB.
Toad Data Modeler and its behavior can be easily customized in several ways to better fit your needs and requirements. You can also leverage the power of scripting and automation to improve your workflow.
To start scripting/customizing, you need to enable Expert Mode first.
To enable Expert Mode
Go to Settings Menu | Options | General and check Expert Mode.
The scripting and customization capabilities include:
Note: Useful information about available classes, methods, functions and properties accessible in Toad Data Modeler can be found in the Reference Guide.
This document is available in the Expert Mode Menu| Reference Guide (with Expert Mode enabled).
Code written in JScript, VBScript or Internal script may be used to access and modify various model objects or even perform model actions such as model renaming, merging, DDL script customization, etc.
Note: Macros are similar to scripts except they can be configured to appear in custom Macro menu or context menu of selected objects.
Scripts/Macros can be accessed via Expert Mode Menu | Customization | Script Explorer.
To create and immediately execute scripts, take advantage of Scripting Window located in Expert Mode Menu.
A package contains various means of customization such as scripts, macros, customized form definitions, data type conversion rules, etc. Packages affect models of various database platforms and versions depending on their Visibility and relations with other packages (Extension, Dependency).
Packages can be accessed via Expert Mode Menu | Customization | Package Explorer.
Graphical representation of objects (classes, properties, methods...) that belong to the selected package. In metamodels, you can create new classes, properties, methods, associations, generalizations... It is very similar to UML Class Diagram.
It is also possible to modify certain application forms (mostly Properties dialogs) and either change existing elements or add custom ones.
1. Scripts and definitions stored in My Package.txg file have the highest priority.
2. Scripts and definitions stored in other user defined packages (distributed as add-ons, add-on packages) have higher priority than scripts and definitions stored in system packages.
3. Scripts and definitions stored in system packages have the lowest priority.