A is integrated software that lets users and applications interact with one or more databases and provides access to the data.

Context: DBMS meaning

A is the collective set of the database, the DBMS, and associated applications.

Context: Database System terminology

is the DBMS capability for creating, modifying, and removing definitions describing how data is organized.

Context: DBMS functional group: Data Definition

is the DBMS capability for insertion, modification, and deletion of the data itself.

Context: DBMS functional group: Update

is the DBMS capability for selecting data by criteria and returning it directly or for further processing.

Context: DBMS functional group: Retrieval

includes security, integrity, concurrency control, and recovery from failures.

Context: DBMS functional group: Administration

In the relational model, data is organized into that use primary keys and declarative queries with joins.

Context: Relational model foundations: tables

A is a designated column (or set of columns) that uniquely identifies rows and is used for cross-table references.

Context: Primary Key meaning

Using primary keys (logical identifiers) instead of disk addresses causes tables to be relocated and resized without expensive database reorganization. This is because primary keys physical storage addresses.

Context: Cause→effect mechanism: primary keys decouple from physical addresses

Relational systems ask for what data is needed, while navigational systems guide how to follow links to find data. Therefore, relational querying is while navigational access is link-following.

Context: Declarative querying vs navigational access

Relational model insists applications search by content rather than following links. This causes applications to use queries and makes the DBMS responsible for finding efficient access paths (query optimization).

Context: Cause→effect chain: content-based search leads to declarative queries and query optimization

Normalization splits complex internal structures into multiple normalized tables connected by logical keys. This causes internal repeating groups (e.g., salary history) to be represented across tables rather than inside a single record. In other words, normalization replaces internal repeating structures with separate tables.

Context: Cause→effect chain: normalization replaces nested/variable repeating structures

NoSQL is described as a family of post-relational databases that became popular in the late 2000s and use different query languages. Therefore, NoSQL is SQL (not necessarily using SQL).

Context: Common confusion: NoSQL does not necessarily use SQL

is the navigational model where applications navigate a linked network of records using keys, sets, or sequential scans.

Context: Navigational model: CODASYL/Network meaning

Availability of direct-access storage media (magnetic disks and drums) in the mid-1960s enabled shared interactive database use instead of tape-based batch processing. This is because random/direct access supports interactive rather than sequential tape scanning.

Context: Cause→effect chain: direct access enables interactive retrieval