Loading content
Relational databases use tables to organize data and are foundational to many modern applications. They provide powerful query languages like SQL and support data integrity through relationships between tables. These features make them a preferred choice for many businesses.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
A relational database organizes data in related tables with defined columns, rows, and relationships.
Edgar F. Codd described the relational model in 1970 to structure data independently of application-specific access paths. Relational databases made that model practical for business applications.
Tables describe entities, primary keys identify rows, and foreign keys connect them. A query joins tables through those relationships to produce a useful view. The model provides structure and integrity; it is a data-model concept, not a particular server product.
A table of tuples and attributes, described mathematically as a relation.
Primary and foreign keys identify records and relationships.
Rules prevent contradictory or orphaned data.
The model supports consistent business-data design and explains SQL systems. Normalization, query cost, and schema rigidity must fit the access pattern.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.