Skip to content
TechToolsHQ
NewsReviewsGuidesTech 101Tech SeriesToolsNewsletter
TechToolsHQ

Independent, research-driven tech coverage — breaking news, in-depth reviews, buying guides, and technical tutorials to help you understand and choose with confidence.

Explore
NewsReviewsGuidesTech 101Tech SeriesFree Tools
Legal
About UsOur AuthorsContact UsPrivacy PolicyTerms of ServiceCopyright & DMCAAffiliate DisclosureEditorial PolicyAdvertise With Us

© 2026 TechToolsHQ. All rights reserved.

Tech Series/Database Management System/What Is an ER Diagram? Entity Sets, Attributes, and Relationship Sets
Database Management System · Part 2 of 2

What Is an ER Diagram? Entity Sets, Attributes, and Relationship Sets

Part 2 of the DBMS series: data models, tables, and the building blocks of an ER diagram.

By Himanshu Bhatt· 2 min read· September 25, 2026

What Is an ER Diagram? — Part 2 of the Database Management System series
Key Takeaways · TL;DR
  • A data model represents the structure of data; the ER model is diagrammatic, the relational model uses tables.
  • A table (relation) is made of rows (records) and columns (fields); a table is an entity set, and each row is an entity.
  • An ER diagram is built from entity sets (rectangles), attributes (ovals, with key attributes underlined), and relationship sets (diamonds).
  • A strong entity set has its own primary key (single rectangle); a weak entity set has none of its own and is identified via a discriminator plus its owner entity's key (double rectangle).
  • A relationship set is strong (single diamond, links two strong entity sets) or weak/identifying (double diamond, links a strong and a weak entity set).
☰ On this page(show)(close)
  • 1.Data Models: ER Model and Relational Model
  • 2.Tables, Rows, and Columns
  • 3.Entity Sets, Attributes, and Relationship Sets
  • 4.Strong and Weak Entity Sets
  • 5.Strong and Weak Relationship Sets
On this page
  • 1.Data Models: ER Model and Relational Model
  • 2.Tables, Rows, and Columns
  • 3.Entity Sets, Attributes, and Relationship Sets
  • 4.Strong and Weak Entity Sets
  • 5.Strong and Weak Relationship Sets
INFO

This is Part 2 of the Database Management System series. It covers data models, the relational model's tables, and the building blocks of an ER diagram — entity sets, attributes, and relationship sets, drawn as rectangles, ovals, and diamonds.

Data Models: ER Model and Relational Model

A data model is used to represent the structure of data in a database. Two of the most common data models are the ER model and the relational model.

  • ER Model: a diagrammatic representation of the logical structure of a database.
  • Relational Model: data represented using a collection of tables.

Tables, Rows, and Columns

The relational model organizes data into tables. Three terms describe the parts of a table:

  • Table or Relation: the structure that holds the data.
  • Row or Record: a single entry in the table.
  • Column or Field: a single property recorded for every row.
Roll_noNameAge
1Gaurav20
2Rahul19
3Dhruv20
4Anjali19

This complete table is called the Student Entity Set, and each row in it represents an entity. There is no separate primary key column here, but Roll_no can still identify each student uniquely.

Entity Sets, Attributes, and Relationship Sets

An ER diagram is built from three parts, each with its own shape:

  • Entity Set: a set of entities of the same type, such as the Student entity set above — drawn as a rectangle.
  • Attributes: the properties that describe an entity, such as Roll_no, Name, and Age — drawn as an oval.
  • Key Attribute: an attribute that identifies each entity uniquely, such as Roll_no — underlined in the diagram.
  • Relationship Set: an association among several entities, such as enrolls in — drawn as a diamond.
The Student entity set is drawn as a rectangle with attribute ovals Roll_no (underlined as the key attribute), Name, and Age. Student connects through the ENROLLS IN relationship set, drawn as a diamond, to the Course entity set.
The Student entity set (rectangle) with its attributes (ovals; Roll_no underlined as the key attribute), connected through the ENROLLS IN relationship set (diamond) to the Course entity set.
●ENTITY SET AND RELATIONSHIP SET
Student
enrolls in
Course
  • •Entity Set: a set of entities of the same type, e.g. all students — drawn as a rectangle.
  • •Attributes: the properties describing an entity, e.g. Roll_no, Name, Age — drawn as an oval.
  • •Key Attribute: identifies each entity uniquely, e.g. Roll_no — underlined in the diagram.
  • •Relationship Set: an association among entities, e.g. enrolls in — drawn as a diamond.

Strong and Weak Entity Sets

Every entity set is either strong or weak, depending on whether it has its own primary key.

  • Strong Entity Set: has its own primary key; drawn as a single rectangle.
  • Weak Entity Set: has no primary key of its own — it is identified only by combining a partial key (called a discriminator) with the primary key of the strong entity set it depends on; drawn as a double rectangle.
A strong entity set, Student, is a single rectangle with a key attribute Roll_no underlined. A weak entity set, Dependent, is a double rectangle with an attribute Name that is not underlined because it has no primary key of its own.
A strong entity set (single rectangle) has its own key attribute; a weak entity set (double rectangle) does not.
✕WEAK ENTITY SET
  • ✕No primary key of its own
  • ✕Identified via a discriminator
  • ✕Drawn as a double rectangle
  • ✕Example - a Dependent of Employee
✓STRONG ENTITY SET
  • ✓Has its own primary key
  • ✓Identified by its own key attribute
  • ✓Drawn as a single rectangle
  • ✓Example - Student by Roll_no

Strong and Weak Relationship Sets

A relationship set is also either strong or weak, depending on the entity sets it connects.

  • Strong Relationship Set: exists between two strong entity sets; drawn as a single diamond.
  • Weak Relationship Set: exists between a strong entity set and a weak entity set. It is also called the identifying relationship, because it is what identifies the weak entity; drawn as a double diamond.
A strong relationship set connects two strong entity sets and is a single diamond, like Student enrolls in Course. A weak relationship set connects a strong and a weak entity set and is a double diamond joined by a double line, like Employee has Dependent.
A strong relationship set (single diamond) links two strong entity sets; a weak, identifying relationship set (double diamond) links a strong entity set to a weak one by a double line.
✕WEAK RELATIONSHIP SET
  • ✕Links a strong and a weak entity set
  • ✕Also called the identifying relationship
  • ✕Drawn as a double diamond
  • ✕Example - Employee has Dependent
✓STRONG RELATIONSHIP SET
  • ✓Links two strong entity sets
  • ✓An ordinary relationship set
  • ✓Drawn as a single diamond
  • ✓Example - Student enrolls in Course

That covers data models, tables, and the building blocks of an ER diagram. The next part builds on these basics.

Drafted with AI assistance from an author outline and edited by TechToolsHQ.

Share
Series: Database Management System

Part 2 — What Is an ER Diagram? Entity Sets, Attributes, and Relationship Sets

Part 2 of 2
← Previous partPart 1 — What Is a DBMS? Data, Databases, and the Client–Server Model
Latest episode in this series.

Enjoying the Database Management System series?

TechToolsHQ is an independent, reader-supported tech platform. If this article saved you time, solved a tough problem, or helped you learn a new skill, consider supporting our work. Your support helps us keep our in-depth series 100% free and updated for everyone.

100% optional · Reader supported · Independent researchSupport our work

Don't miss the next deep-dive

Weekly breakdowns of the tools students and builders actually use.

No spam·Unsubscribe any time·Privacy-first