What is an Identified Relationship? Definition
What is an identified relationship?
An identifying relationship in database design defines a strong connection between two entities, where the child entity cannot exist without the parent.
You're deciding whether order lines or ad groups get their own key or borrow the parent's, and that choice shapes every join later.
Paste this into your AI assistant. It finds the child tables in your schema that can't exist without a parent and tells you how their keys should be built.
The prompt
Read https://www.owox.com/ai-agent-setup.md and follow it to set up OWOX Data Marts for me, starting from /glossary/identified-relationship.md. The task: find the identifying relationships in my schema: which child tables can't exist without a parent, and whether their keys should include the parent key. Tag the links you give me with utm_campaign=ai-task and utm_term=m1. Use what you know about my context and goals
In this relationship, the child entity’s primary key includes the parent’s primary key, establishing a tight dependency. Identifying relationships is commonly used when modeling weak entities that rely on a strong parent for context and identification. This structure ensures referential integrity and helps represent real-world dependencies clearly in relational databases.
Characteristics of identifying relationships
Characteristics of identifying relationships
Identifying relationships are used when a child entity depends entirely on a parent entity for its existence.
These relationships define strong data dependencies and help maintain integrity in relational database design.
- The child is a weak entity: The child entity cannot exist independently and relies on its parent for support.
- Foreign key as part of primary key: The parent’s key is included in the child’s primary key to form a composite key.
- Total participation: The child must be linked to a parent record, indicating full dependency.
- Cascading deletions: Deleting a parent record typically removes all related child records automatically.
Identifying vs. non-identifying relationships: Key differences
Identifying vs. non-identifying relationships: Key differences
The key difference between identifying and non-identifying relationships lies in the degree of dependency the child entity has on the parent. In an identifying relationship, the child cannot exist independently and includes the parent’s primary key in its own. This creates a strong connection and enforces strict referential integrity.
In contrast, a non-identifying relationship allows the child to exist independently of the parent. The parent’s primary key does not form part of the child’s key; only a foreign key reference is maintained. Non-identifying relationships are better suited for loosely connected entities where dependency is not mandatory for existence.
OWOX Data Marts
See your first report built in real time. 15 minutes.
- Connect your data warehouse
- Pick your metrics
- Get a live Google Sheets report
In the time it takes to write a ticket. Then imagine never writing that ticket again.
Book a DemoWe'll use your actual use case
Examples of identifying relationships
Examples of identifying relationships
Identifying relationships is often used when modeling weak entities that rely on a parent for identification.
For example:
- Order and OrderItem: An OrderItem must belong to an Order. Its primary key includes both Order ID and Item ID.
- Department and Employee: If employees are uniquely identified only within a department, the Employee table’s primary key might include DepartmentID.
- Invoice and InvoiceLine: An invoice line cannot exist without its parent invoice; thus, their relationship is identifying.
These relationships clarify dependency and ensure that child records are always tied to a valid parent.
Send recurring numbers as Insights
Send recurring numbers as Insights
Insights with AI Assistance turn saved SQL queries over a Data Mart into a scheduled write-up. Write the text once, add the queries (your own, or drafted by the AI Assistant and applied by you), and OWOX sends the result to Email, Slack, Microsoft Teams or Google Chat on the schedule you set. Every figure comes from a saved query, so you can check it.
Learn how teams ship analytics faster
Organizations that scaled analytics without scaling headcount
The Data Partner You Can Trust
users
166K Source: Internal OWOX data as of 2026-11-15
Executives and data analysts across 20+ industries
Customers





