Previous  Top  Next

Mapping large databases with MapForce

When using databases with many tables in mappings, MapForce displays all database relations between the imported tables, of the whole database. This is due to the fact that the application cannot automatically decide which tables will be used in the mapping process, all possibilities have to be covered.

This may lead to inconveniently large tree structures if all tables are selected in a single database component. It is however possible to create multiple database components, of the same database, which only use/import those tables that are needed for the mapping process. This method also makes for a more intuitive mapping.

E.g.

In a production company, various components are assembled to produce customer defined units. Before delivery, the units undergo a unit test and all results are stored in a database.

At some point during the prototype testing phase, it is discovered that a batch of components are faulty, and a recall has to be initiated. The goal of the mapping is to generate a list of all affected customers to whom a letter must be sent.

In this case the mapping defines:

For the ComponentType name = "Prototype" AND the Manufacturer = "Noname",

Select all related Customers and their requisite details.

The relationship diagram of the example database discussed in this section, is shown below: