One-to-Many Relationships - Teradata Vantage - Analytics Database

Database Design

Deployment
VantageCloud
VantageCore
Edition
VMware
Enterprise
IntelliFlex
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Publication Date
June 2022
Content Type
Administration
User Guide
Publication ID
B035-1094-172K
ft:locale
en-US
ft:lastEdition
2025-11-21
dita:mapPath
ogg1628096130566.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
ft:sourceId
dita
dita:id
zqc1472244571611
lifecycle
lifecycle
Product Category
Teradata Vantageā„¢

Assume two entities, A and B.

A 1:M relationship exists between entity A and entity B when each occurrence of entity A is related to 0, 1, or more occurrences of entity B, while each occurrence of entity B is related to at most one occurrence of entity A.

1:M relationships are commonly seen in real-world situations. For example, each department has many employees, but each employee has only one department.

1:M relationships are graphed as follows:



Modeling 1:M Relationships

1:M relationships are modeled by placing the primary key of entity A as a foreign key component of entity B.

Example

Because 1:M relationships are asymmetric, the entity A key must be placed in entity B. The reciprocal relationship does not model the same E-R relationship.