Denormalize

lecture lab details note for this lab we will only focus on the connection 5g warehouse erd only denormalization rules any table in the relational model that is labeled as a “ d ” with a 1\ m cardinality or labeled as “ b ” will be defined as as an object array or map on the parent table triggered by rule #1, before denormalizing “ d ” or “ b ” tables that act as arrays or maps, interrogate them to determine how best to denormalize them back into their parent table any table in the relational model that is labeled as “ d ” with a cardinality of m 1 will act as either an object or a list of fields on its parent table denormalization for personalization rules always remember to review the customer use cases when building out the data model keep in the mind the following streaming segmentation does not have access to lookup tables at evaluation time only the traits and segment memberships of a profile are accessible for personalizing content remeber to reference the connection 5g training scenario pdf during this lab! step 1 – fill in the individual profile table write in the fields that need to be de normalized back on the customer account table from any related “ b ” or “ d ” schemas reviewing the use cases above what additional fields are required to support streaming segmentation and/or personalization? add those fields to the table step 2 – fill in the experience event tables write in the fields that need to be denormalized back into the billing and order’s table from any related “ b ” or “ d ” tables reviewing the use cases above what additional fields are required to support streaming segmentation and/or personalization? add those fields to the table step 3 – fill in the lookup tables write in the fields that need to be de normalized back into the product lookup table from any related “ b ” or “ d ” tables reviewing the use cases above what additional fields are required to support streaming segmentation and/or personalization? add those fields to the table review