Maps 1–4
Map 1 — The Operating Spine
BUSINESS CONTINUITY
↓
Availability ─ Integrity ─ Transaction Performance
↓
Database Technology Support + Database Operations Support
platform stored-data service
Interpretation: continuity is the driver; the three goals describe service health; Technology Support manages the platform while Operations Support manages the data/processes running on it.
Source: pp. 166–168.
Map 2 — Database Object Vocabulary
DATABASE = stored data collection
INSTANCE = running DBMS execution controlling storage
SCHEMA = organized subset/container of database objects
NODE = one computer/component in a distributed database
Trap: database and instance are not automatic synonyms.
Source: pp. 168–170.
Map 3 — Administrator Role Map
Production DBA → reliability | tuning | backup/recovery | failover
Application DBA → application databases across environments
Procedural DBA → stored procedures | triggers | UDFs
Development DBA → design | sandbox | special-use development
NSA → storage arrays | storage hardware/software
Changed fact: a failed trigger points toward Procedural DBA; a failed storage array points toward NSA even if Production is affected.
Source: pp. 170–173.
Map 4 — Architecture Decision Tree
One system/place? → CENTRALIZED
Multiple nodes? → DISTRIBUTED
├─ autonomous component DBs → FEDERATED
│ ├─ component-built schemas → LOOSE
│ └─ integrated published schema → TIGHT
└─ centrally controlled components → NON-FEDERATED
Key: Distributed asks how many places/nodes? Federation asks who retains control/autonomy?
Source: pp. 174–176.