TheHingineer

  • DBMS


  • DBMS Part-1

  • DBMS Part-2

  • DBMS Part-3

  • DBMS Part-4

  • DBMS Part-5

  •  Converting ER Diagram to Tables in DBMS


     Pehle Samjho: Kya aur Kyun?

    ER (Entity-Relationship) diagram ek conceptual design hai, jisme hum real-world cheezein (like Student, Course) ko entities, attributes, aur relationships ke form mein dikhate hain.

    Lekin database banane ke liye humein is design ko tables mein badalna padta hai, taaki hum data ko store kar saken.

     Step-by-Step Conversion Process

     Step 1: Entities ko Table mein Convert karo

    Jo bhi entity hoti hai ER diagram mein, usko ek table bana dete hain.

     Example:

    Entity: Student
    Attributes: StudentID, Name, Age

    Toh Table banega:

    Student (
    StudentID PRIMARY KEY,
    Name,
    Age
    )
     

     Step 2: Relationship ko Convert karo

    Agar relationship Many-to-Many hai, toh uske liye nayi table banate hain.

     Example:

    Entities:

    • Student (StudentID, Name, Age)

    • Course (CourseID, CourseName)
      Relationship: Enrolls (with EnrollmentDate)

    Enrolls ka Table banega:

    Enrolls (
    StudentID FOREIGN KEY,
    CourseID FOREIGN KEY,
    EnrollmentDate,
    PRIMARY KEY (StudentID, CourseID)
    )

    Is table mein dono entities ke primary keys ko foreign key bana dete hain, aur extra attribute bhi add kar sakte hain.

     Step 3: Weak Entities ka Handle

    Weak entities woh hoti hain jinke paas khud ka primary key nahi hota. Yeh kisi strong entity pe depend karti hain.

     Example:

    Dependent → depends on Employee

    Table banega:

    Dependent (
    DependentName,
    EmployeeID FOREIGN KEY,
    PRIMARY KEY (DependentName, EmployeeID)
    )
     

     Step 4: Multi-Valued Attributes

    Agar kisi entity ka attribute multiple values store karta hai (jaise phone numbers), toh uske liye naya table banate hain.

     Example:

    Student ke paas multiple phone numbers hain.

    Toh naya table banega:

    StudentPhone (
    StudentID FOREIGN KEY,
    PhoneNumber,
    PRIMARY KEY (StudentID, PhoneNumber)
    )
     

     Step 5: Generalization / Specialization ka Handle

    Agar ek entity ke multiple specific types hain, toh:

    • Ek table hota hai general entity ke liye

    • Har specific entity ke liye alag table banta hai, jisme foreign key hoti hai general table ka reference.

     Example:

    Employee general hai
    Manager aur Engineer specific roles hain

    Tables:

    Employee (
    EmpID PRIMARY KEY,
    Name
    )

    Manager (
    EmpID PRIMARY KEY FOREIGN KEY REFERENCES Employee,
    Bonus
    )

    Engineer (
    EmpID PRIMARY KEY FOREIGN KEY REFERENCES Employee,
    Skill
    )


     Summary Table 

    ER Diagram Ka PartRelational Table Mein Kaise Convert Hota Hai
    EntityTable banti hai, primary key ke saath
    AttributeColumn banta hai table mein
    Many-to-Many RelationshipNaya table banta hai with foreign keys
    Weak EntityTable with foreign key + partial key
    Multi-Valued AttributeNaya table banta hai
    Generalization / SpecializationParent-child jaisa relation with foreign key

     Example ER Diagram se Table me Conversion :

    Converting ER Diagram to Tables in DBMS
     

    Tables banenge:

    • Student(StudentID, Name, Age)

    • Course(CourseID, CourseName)

    • Enrolls(StudentID, CourseID, EnrollmentDate)


     Conclusion 

    • -> ER diagram ek design hai, jisko relational model (table format) mein badalna padta hai.

    • -> Har entity → ek table

    • -> Har attribute → ek column

    • -> Relationship → foreign keys ya naya table

    • -> Special cheezein (multi-valued, weak entity) → handled with care

    Scroll to Top