Loading Databases
MDS loads data dictionary information for each of the selected databases into the
MDS repository. The actual data in the database tables is not loaded.
The option you use to load databases into the MDS repository determines what databases
the DDL Gateway keeps in sync. The difference is in how the DDL Gateway handles newly
created users and databases in the Teradata Database System.
If you load “All” databases, the DDL Gateway will automatically add new databases
and users that are created in the Teradata Database System to the MDS repository.
In other words, “All” indicates that you want the MDS repository to contain all databases
in the Teradata Database System.
If you load “Selected” databases, the DDL Gateway will NOT add new databases and users
that are created in the Teradata Database System to the MDS repository. The DDL Gateway
will maintain only those databases selectively loaded into the MDS repository.
If you load “All but Selected” databases – the DDL Gateway will automatically add
new databases and users that are created in the Teradata Database System to the MDS
repository. It, however, maintains the list of those databases that were excluded
on the initial load and ignores all DDLs for those databases. Databases that were
originally loaded but are later unloaded are considered to be databases that are excluded.
For all other DDLs, the DDL Gateway will update the repository for loaded databases
and will ignore DDL for databases that are not loaded into the repository.
If you do not load any databases for a Teradata Database System, the MDS DDL Gateway
will not track that system even if Automatic DIM Update is enabled for the system.
Before enabling DIM Update, load all databases to be maintained. If there is a lengthy
time between the initial load of the databases and when DIM Update is enabled, resync
all databases before enabling DIM Update.