Database Schema Notation Symbols Explained: a Visual Guide

Every database diagram you've ever seen uses symbols to communicate structure lines, boxes, arrows, crow's feet, diamonds. But if those marks look like hieroglyphics to you, you're not alone. Understanding database schema notation symbols is the difference between reading a data model and staring at a confusing diagram. Whether you're a developer joining a new team, a student learning relational database design, or someone reviewing an ERD for a project, these symbols are how the entire structure of your data gets communicated visually.

What Are Database Schema Notation Symbols?

Database schema notation symbols are the visual markers used in entity-relationship diagrams (ERDs) and database schemas to represent tables (entities), their attributes (columns), and the relationships between them. Think of them as the alphabet of database design. Instead of writing out "a customer can have many orders, but each order belongs to only one customer," a diagram uses a specific line, a symbol at each end, and labels to say the same thing in a picture.

Different schema notation systems use slightly different symbols to represent the same concepts. The most common notations you'll run into are:

Chen notation uses diamonds for relationships, ovals for attributes, and rectangles for entities
Crow's foot notation (also called Martin or IE notation) uses lines with crow's-foot shapes at the ends to show cardinality
Bachman notation uses arrows and labeled lines between entities
UML class diagrams adapted from software engineering with class-box-style entities

Each system solves the same problem making database structure readable at a glance but they do it with their own visual language.

Why Do the Symbols Look Different in Every Diagram I See?

The short answer: there's no single universal standard. Different tools, teams, and traditions picked different notations over the decades. Chen introduced his notation in 1976, and it was designed for academic clarity. Crow's foot notation became popular in the 1980s through James Martin's work and later got adopted by most commercial database modeling tools. UML brought its own approach from object-oriented software design.

In practice, most working database teams today use IE (Information Engineering) notation, which is the crow's foot style. You'll find it in tools like MySQL Workbench, dbdiagram.io, Lucidchart, and Microsoft Visio. If you're reading older textbooks or academic papers, you'll more likely encounter Chen notation. And if your team comes from a software engineering background, UML class diagrams might show up instead.

The important thing is that once you learn one notation well, picking up another is quick. The underlying concepts entities, attributes, primary keys, foreign keys, and cardinality don't change. Only the symbols do.

What Do the Most Common Symbols Actually Mean?

Here's a breakdown of the symbols you'll see most often, starting with crow's foot notation since it's the most widely used in professional settings.

Entities (Tables)

Represented as rectangles. Each box is a table in your database. The table name goes at the top, and the columns (attributes) are listed inside. In Chen notation, these are also rectangles, but you'll sometimes see a double-bordered rectangle for a weak entity one that depends on another entity for its identity.

Attributes (Columns)

In crow's foot notation, attributes are listed inside the entity rectangle. In Chen notation, they appear as ovals connected to the entity by lines. The primary key attribute is usually underlined or marked with "PK." Attributes that can be null may be marked differently depending on the tool.

Relationships

This is where the notations differ the most:

Crow's foot notation: Lines connect entities. At each end of the line, you'll see one of three symbols: a single line (one), a crow's foot (many), or a circle (zero). A crow's foot with a circle means "zero or many." A single line with a short perpendicular bar means "exactly one."
Chen notation: Relationships are diamond shapes placed between the two entity rectangles, with lines connecting them. Cardinality is shown with "1," "M," or "N" labels on the lines.
Bachman notation: Uses directed arrows from the "many" side to the "one" side, with labels describing the relationship.

Cardinality and Modality

Cardinality tells you how many of one entity relate to another (one-to-one, one-to-many, many-to-many). Modality (also called participation) tells you whether the relationship is required or optional. In crow's foot notation:

Required (one): A solid line or a single perpendicular bar at the end of the relationship line
Optional (zero or one): A circle (also called an "o" or "ring") at the end
Many: The crow's foot symbol (three prongs like a bird's foot)
One and only one: A single short line (sometimes called a "dash" or "tee")

How Do I Read a Crow's Foot Diagram Step by Step?

Let's walk through a practical example. Say you see a diagram with two boxes: Customer and Order. A line connects them. On the Customer side, you see a single perpendicular bar (one and only one). On the Order side, you see a crow's foot with a circle (zero or many).

Reading left to right: "Each customer has zero or many orders." Reading right to left: "Each order belongs to one and only one customer." That's a classic one-to-many relationship, and the symbols told you that in a second without a single word of explanation.

Now imagine a third box, Product, connected to Order. The line between Order and Product might show many on both sides that's a many-to-many relationship. In a real database, this usually means there's a junction table (like OrderItem) in between, even if it's not shown in a high-level diagram.

What Are the Key Symbols I Should Memorize?

If you want a quick mental cheat sheet, here are the most important symbols in crow's foot notation:

Rectangle an entity (table)
Underlined text primary key attribute
Single line (perpendicular bar) exactly one
Circle (o) zero (optional)
Crow's foot (three-pronged fork) many
Circle + crow's foot zero or many
Bar + crow's foot one or many
Bar alone one and only one
Circle alone zero or one
Dashed or thin line non-identifying relationship (the child can exist independently)
Solid or thick line identifying relationship (the child depends on the parent's key)

That's really it. Everything else in a standard ERD is built from combinations of these.

What Common Mistakes Do People Make When Reading Schema Diagrams?

Mixing up "many" and "one" ends. The crow's foot symbol always goes on the "many" side. If you flip which end has it, you'll misunderstand the entire relationship. A simple trick: the crow's foot fans out, like multiple items spreading out from a point. It always points toward the table that holds the many.

Ignoring modality. Cardinality tells you the maximum number. Modality tells you the minimum. A circle means zero is allowed that the relationship is optional. Many people skip this detail and assume a relationship is required when the diagram explicitly says it's optional, or the other way around.

Confusing notations. A diamond in Chen notation means "relationship." A diamond in another context might mean something else entirely. If you don't know which notation a diagram uses, look for a legend or check what tool created it.

Assuming many-to-many relationships can exist directly. In a relational database, they can't you always need an intermediate table. But in a high-level ERD, you might see a many-to-many line drawn directly between two entities. That's a conceptual shortcut, not the final table design.

Where Can I Practice Reading These Symbols?

The best way to learn is to look at real diagrams. Here are a few approaches:

Use a free tool like dbdiagram.io to build small schemas and see how the notation renders
Look at the schema diagrams that come with open-source projects on GitHub
Reverse-engineer an existing database in MySQL Workbench or pgModeler it auto-generates ERD diagrams with crow's foot symbols
Study the differences between Bachman notation and IE notation side by side to sharpen your ability to switch between styles

After reading a dozen diagrams, the symbols become second nature. You won't even think about what the crow's foot means you'll just see "many" automatically.

Quick Reference Checklist

Identify which notation the diagram uses (Chen, crow's foot, Bachman, or UML) before trying to read it
Look for the legend or key in the diagram if none exists, check what tool generated it
Read each relationship line from both directions (left-to-right and right-to-left)
Check both cardinality (how many max) and modality (required or optional) at each end
Remember: crow's foot = many, single bar = exactly one, circle = zero/optional
If you see a many-to-many direct line, expect a junction table in the actual implementation
Practice by reverse-engineering one real database schema per week until the symbols feel natural