Option	Description
Select Schema/Owner/Database	Contains existing Schemas/Owners/Users in your model. Select --None-- from the list to remove the existing schema from objects you mark in the Select types of objects section.
Assign to objects where value is not defined	Assigns schema/owner to objects, which have none assigned yet.
Confirm before assignment checkbox	Confirmation dialog for each object where schema is being assigned/removed will be displayed.
Select types of objects area	Mark objects which should be assigned a Schema/Owner.

Infer Relationships

Features and Tools > Tools > Infer Relationships

This feature tries to map Primary Keys or Alternate Keys to identically named attributes in other entities.

Conditions:

Mapping is performed between key and non-key attributes. In other words, if identically named attributes are part of primary key in various tables, e.g. ID column in table Customer and ID column in table Order, the two ID columns will not be mapped and no relationship will be created.
Names must be identical and data type must be the same, including parameters.
Non-identifying relationships are created by default. In case you need an identifying relationship, edit the automatically added relationship and change its type to identifying manually.

To run the Infer Relationship function

Select Tools | Infer Relationship.

Note: Relationships created this way will be marked with a To-Do task prompting you to check whether the relationship has been created correctly.

Example:

Model with no relationships. See the Customer ID column in tables Customer and Order Record.
In table Film there is an alternate key with two columns Title and Director. Identically named columns are in table Customer Rating.

Run the Infer Relationship function and see the result:

Infer Relationships and Reverse Engineering

The same tool can be used automatically during reverse engineering.

Create a new connection or edit an existing stored connection and check the Infer Relationships checkbox to activate this feature.

Version Control

Git Version Control

Features and Tools > Version Control > Git Version Control

To configure git

Configure Toad Data Modeler to work with Git in Options | Application | Version Control System. The values set here will be your default values for setting up new repositories in Toad Data Modeler

Select Git in Type
Set paths to your Git client and working directory for your repository
Click Apply and Initialize Local Repository. The folder will be created (if it does not exist) and initialized
Enter a path to the remote repository, user name, and password
Click Apply and Clone Repository

Git application view

The following Git commands are displayed in Application View toolbar when you work with a model that is tracked:

Add Existing Models to Project to display the Git commands in Application View

Application View Button	Description
Version Control System Settings	Opens Options page where you can set the Version Control System preferences
Refresh	Refreshes file status in Toad Data Modeler
Add to Index	Adds the file to the list of tracked files
Remove from Index	Removes the file from the list of tracked files
Commit	Commits changes
Push	Pushes the committed changes into the remote repository
Pull	Pulls the current state from the remote repository
Fetch	Fetches information about the current state of the remote repository
Information	Displays information about the commit and its author
History Browser	Allows you to browse different versions of the file, merge and compare them and create change script

Please select your product:

To serve you better, please complete the Purpose of your Chat:

Recommended Solutions for Your Problem

Toad Data Modeler 6.4 - User Guide

Schema/Owner/Database Assignment

Infer Relationships

Infer Relationships and Reverse Engineering

Version Control

Git Version Control

Git application view