Bookshelf Home | Contents | Index | Search | PDF

Siebel Marketing Guide > External Data Mapping > Understanding Joins >

Parent and Child Joins

---

When you establish a join, you define a connection between two tables. One table is the parent and the other table is the child. You connect the parent table to the child table using at least one field that they have in common. By defining these join pairs, you can connect each of the relevant tables in your data warehouse. A join connection can be unidirectional or bidirectional. This section describes unidirectional and bidirectional joins.

Unidirectional join connection. By default, each join record in the Marketing Repository is a unidirectional join. The Marketing Server retrieves child information when it queries a parent record, but will not retrieve parent information when it queries a child record. This is the default behavior of a join in the Marketing Repository.

Figure 3 shows an example of unidirectional joins between four tables. Tables B and C are child tables when connected to A and are parent tables when connected to D.

Figure 3. Sample Table Joins

Bidirectional join connection. Most table joins in your physical database can be bidirectional. To create a bidirectional join in Siebel Marketing, you need to define two joins, one in which A is the parent and B is the child, the other in which B is the parent and A is the child.

Bookshelf Home | Contents | Index | Search | PDF