What This Document Is
These notes cover the process of mapping Extended Entity Relationship (EER) diagrams into relational database schemas. It focuses on how different EER constructs – entities, attributes, relationships (one-to-one, one-to-many, many-to-many), and weak entities – are translated into tables and keys within a relational model. The notes illustrate the mapping process with diagrams showing both the EER model and the resulting relational schema fragments.
Why This Document Matters
This study guide is essential for students in Db Sys Concepts & Design (CS 6400) at Georgia Tech preparing for the second exam. Understanding EER to relational mapping is a core skill for database design, allowing you to implement conceptual models in a practical database system. It’s used when you need to translate a visual representation of data requirements into a functional database structure.
Common Limitations or Challenges
This document provides a focused overview of the mapping *process* but does not cover advanced topics like normalization or SQL implementation. It assumes a foundational understanding of EER diagrams and relational database concepts. It also doesn’t provide practice problems or complete examples – it’s a conceptual guide, not a problem set.
What This Document Provides
The notes detail how to map:
* Single-valued and composite attributes.
* Multivalued entity types into separate relations.
* One-to-one, one-to-many, and many-to-many relationship types.
* Identifying and non-identifying relationships with weak entities.
* The use of primary and foreign keys to maintain relationships in the relational model.
This preview *does not* include detailed examples of normalization, SQL code, or comprehensive case studies. It focuses solely on the initial translation from EER diagrams to relational schemas.