[03/Santee/04]

To unify different business keys from various sources

Same-as-Link (SAL) in BV

It complicates the data integration process

False

False

False

Composite Business Keys in Hubs = Allowing a concept to have different business keys in different sources and tables Same-as-Link (SAL) = An alternative extension for Composite Business Keys in Hubs in the context of BV Multiple hubs for each key structure = A less efficient but still valid approach for handling different business key structures in hubs Flow.BI = Collects different structures and unionizes them to handle different business key structures in hubs

To uniquely identify a record in a database using multiple attributes

Employees can work in different departments

Structural differences in business keys

Creating multiple hubs for each key structure

A combination of two or more attributes uniquely identifying a record

Employees can work in different departments

Creating one hub per business key structure

True

False

True

False

False

True

True

Composite Business Keys = Combination of two or more attributes within a database table that uniquely identify a record Multiple Hubs = Design approach generating one hub with maximum columns to cover all business keys Standard Design = Believed to be the most efficient approach for handling different business key structures Same-as-Link (SAL) = Alternative approach to generating one hub per business key structure or other designs

Employee ID and Department ID = Ensuring uniqueness for employees working in different departments Single attribute like an employee ID = Insufficient for ensuring uniqueness in a table storing employee information Combination of two or more attributes within a database table = Uniquely identifying a record in a database Multiple columns or attributes = Uniquely identifying a record within a table

Multiple Hubs for each key structure = Considered a trade-off due to potential inefficiency Adjusting rules to generate one hub per business key structure = Possible alternative to standard design for efficiency Standard Design = Believed to be the most efficient approach for handling different business key structures Same-as-Link (SAL) = An extension of the concept of Composite Business Keys in Hubs

Using multiple columns or attributes rather than a single attribute = Purpose of using Composite Business Keys in Hubs Creating multiple hubs for each key structure = Considered less efficient in the standard design Adjusting rules to generate one hub per business key structure = Potential adjustment to the standard design for efficiency Belief in the standard design as the most efficient = Implication of the approach for handling different business key structures