Strong Entity

Definition

A strong entity (also called a regular entity) is an entity that has a complete set of attributes sufficient to uniquely identify it on its own, without needing to reference any other entity. Every strong entity possesses its own primary key, and its existence in the database does not depend on any other entity.

Worked Example

In the college database, Student is a strong entity set: every student has a Roll_No that uniquely identifies them, independent of any other entity. Course, Department, and Faculty are also strong entities — a Department (e.g., "Computer Science", Dept_Code = "CS") can exist in the database and be fully identified even if it currently has zero students or courses linked to it.

Edge Cases

• The defining test for "strong" is independence of identification, not independence of existence in the real world. A strong entity can still participate in mandatory relationships (e.g., a rule that every course must belong to a department) — it is still strong as long as it has its own key.
• A strong entity is drawn with a single-line rectangle in ER diagrams, contrasted with the double-line rectangle used for weak entities.
• Do not confuse "strong entity" with "total participation." An entity set can be strong (has its own key) yet participate totally in a relationship (every instance must relate to something) — these are two independent properties.
• Most entity sets in a typical schema are strong; weak entities are the exception, reserved for things that genuinely cannot be identified without an owner.

Key Takeaways / Interview Q&A

Q: What is the single most important test to decide if an entity is strong? A: Ask: "Can I write a primary key for this entity set using only its own attributes, with no reference to another entity set?" If yes, it is strong.

Q: Is every strong entity mandatory in every relationship it takes part in? A: No — being strong (self-identifiable) is unrelated to participation constraints (total/partial, covered in 6.14). A strong entity can have optional (partial) participation in a relationship.

Q: In ER-to-relational mapping, how is a strong entity handled differently from a weak entity? A: A strong entity's table uses its own primary key directly. A weak entity's table must additionally embed the owner's primary key as part of its own composite key (see 6.4 and 6.21).