Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 85 views

    EXP.2. Mapping EER To Relational Schema Model

    Uploaded by

    03 Bhingle Abhishek
    This document outlines the steps to map an entity-relationship (EER) model to a relational database schema. It discusses how to map various EER model components, including: 1. Regular entity types are mapped to tables, with attributes and primary keys. 2. Weak entity types are similarly mapped, and the primary key of the owner entity is added as a foreign key. 3. Binary 1:1 relationships can use foreign keys, a merged table, or a cross-reference table to represent the relationship. 4. Binary 1:N relationships use foreign keys, with the "N" entity's primary key in the "1" entity table. The document concludes that

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    EXP.2. Mapping EER To Relational Schema Model

    Uploaded by

    03 Bhingle Abhishek
    85 views3 pages
    This document outlines the steps to map an entity-relationship (EER) model to a relational database schema. It discusses how to map various EER model components, including: 1. Regular entity types are mapped to tables, with attributes and primary keys. 2. Weak entity types are similarly mapped, and the primary key of the owner entity is added as a foreign key. 3. Binary 1:1 relationships can use foreign keys, a merged table, or a cross-reference table to represent the relationship. 4. Binary 1:N relationships use foreign keys, with the "N" entity's primary key in the "1" entity table. The document concludes that

    Original Title

    03_exp2_abhishek

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document outlines the steps to map an entity-relationship (EER) model to a relational database schema. It discusses how to map various EER model components, including: 1. Regular entity types are mapped to tables, with attributes and primary keys. 2. Weak entity types are similarly mapped, and the primary key of the owner entity is added as a foreign key. 3. Binary 1:1 relationships can use foreign keys, a merged table, or a cross-reference table to represent the relationship. 4. Binary 1:N relationships use foreign keys, with the "N" entity's primary key in the "1" entity table. The document concludes that

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    85 views3 pages

    EXP.2. Mapping EER To Relational Schema Model

    Uploaded by

    03 Bhingle Abhishek
    This document outlines the steps to map an entity-relationship (EER) model to a relational database schema. It discusses how to map various EER model components, including: 1. Regular entity types are mapped to tables, with attributes and primary keys. 2. Weak entity types are similarly mapped, and the primary key of the owner entity is added as a foreign key. 3. Binary 1:1 relationships can use foreign keys, a merged table, or a cross-reference table to represent the relationship. 4. Binary 1:N relationships use foreign keys, with the "N" entity's primary key in the "1" entity table. The document concludes that

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 3

    EXP.2. Mapping EER to Relational schema model.

    Aim: Mapping EER to Relational schema model.

    Theory: Mapping Rules

    Step 1: Regular Entity Types


    Create an entity relation for each strong entity type. Include all single-valued attributes. Flatten
    composite attributes. Keys become secondary keys, except for the one chosen to be the primary
    key.

    Step 2: Weak Entity Types


    Also create an entity relation for each weak entity type, similarly including its (flattened) single-
    valued attributes. In addition, add the primary key of each owner entity type as a foreign key
    attribute here. Possibly make this foreign key CASCADE.

    Step 3: Binary 1:1 Relationship Types


    Let the relationship be of the form [S]——<R>——[T].
    1. Foreign key approach: The primary key of T is added as a foreign key in S. Attributes
    of R are moved to S (possibly renaming them for clarity). If only one of the entities has
    total participation it's better to call it S, to avoid null attributes. If neither entity has total
    participation nulls may be unavoidable. This is the preferred approach in typical cases.
    2. Merged relation approach: Both entity types are stored in the same relational table,
    “pre-joined”. If the relationship is not total both ways, there will be null padding on
    tuples that represent just one entity type. Any attributes of R are also moved to this table.
    3. Cross-reference approach: A separate relation represents R; each tuple is a foreign key
    from S and a foreign key from T. Any attributes of R are also added to this relation. Here
    foreign keys should CASCADE.
    Approach Join cost Null-storage cost
    Foreign key 1 low to moderate
    Merged relation 0 very high, unless both are total
    Cross-reference 2 none

    Step 4: Binary 1:N Relationship Types


    Let the relationship be of the form [S]——N<R>1——[T]. The primary key of T is added as a
    foreign key in S. Attributes of R are moved to S. This is the foreign key approach. The merged
    relation approach is not possible for 1:N relationships. (Why?) The cross-reference approach
    might be used if the join cost is worth avoid null storage.

    Step 5: Binary M:N Relationship Types


    Here the cross-reference approach (also called a relationship relation) is the only possible way.

    Step 6: Multivalued Attributes


    Let an entity S have multivalued attribute A. Create a new relation R representing the attribute,
    with a foreign key into S added. The primary key of R is the combination of the foreign key and
    A. Once again this relation is dependent on an “owner relation” so its foreign key should
    CASCADE.

    Step 7: Higher-Arity Relationship Types

    Here again, use the cross-reference approach. For each n-ary relationship create a relation to
    represent it. Add a foreign key into each participating entity type. Also add any attributes of the
    relationship. The primary key of this relation is the combination of all foreign keys into
    participating entity types that do not have a max cardinality of 1.
    Conclusion:- For given case study EER relational mapping is done successfully.

    You might also like