Design the physical data model

https://knobit.org/id/activity/LO-6

dcterms:license	https://creativecommons.org/licenses/by/4.0/
owl:sameAs	https://bitbucket.org/reffa/ontology/id/activity/data-modelling/06-physical
rdfs:comment	Stage 4 (Physical) of the data-modelling skill: produces 04-physical/physical-model.yaml and passes the stage's validation gate. en
rdfs:label	Design the physical data model en
rdfs:label	Füüsilise andmemudeli kujundamine et
requires knobit	Recognises a constraint claimed by a rule and missing from the schema
requires knobit	Recognises a declared constraint the target platform does not enforce
requires knobit	Recognises an unmanaged duplicate column
requires knobit	Recognises logical entities merged into one table
requires knobit	Recognises a stored derived or summary value
requires knobit	Recognises a lossy or unconstrained vertical split
requires knobit	Recognises an entity split into clone tables by value
requires knobit	Recognises rolled-up subtypes losing conditional constraints
requires knobit	Recognises rolled-down subtypes losing supertype constraints
requires knobit	Recognises a hierarchy encoded redundantly
requires knobit	Recognises content held outside the database by reference
requires knobit	Recognises a surrogate key without natural-key uniqueness
requires knobit	Recognises a surrogate value with meaning, reused or renumbered
requires knobit	Recognises an undeclared foreign key
requires knobit	Recognises a referential action destroying what should survive
requires knobit	Recognises a changeable value list fixed in the DDL
requires knobit	Recognises a physical domain differing from the logical domain
requires knobit	Recognises binary floating point used for an exact quantity
requires knobit	Recognises a business fact held in physical row order
requires knobit	Recognises an index set not derived from access paths
requires knobit	Recognises an overwrite where history is required
requires knobit	Recognises inconsistent validity periods in a versioned table
requires knobit	Recognises a reference to a versioned table by business key alone
requires knobit	Recognises a soft delete the constraints do not understand
requires knobit	Recognises a fact table of mixed grain
requires knobit	Recognises a measure without stated additivity
requires knobit	Recognises a nullable foreign key on a reporting join path
requires knobit	Recognises a sentinel value standing in for null
requires knobit	Recognises a null with a business meaning
requires knobit	Routes a defect to the deliverable responsible for it
requires knobit	Explains controlled denormalisation
requires knobit	Explains the implementation options for subtypes
requires knobit	Explains referential integrity and referential actions
requires knobit	Explains exact and approximate numeric types
requires knobit	Explains null semantics and three-valued logic
requires knobit	Explains value sets held as reference data
requires knobit	Explains index design from access paths
requires knobit	Explains history strategies and validity-period conventions
requires knobit	Explains grain and additivity in dimensional models
requires knobit	Explains vertical and horizontal partitioning of tables
requires knobit	Explains consistency of content stored by reference
requires knobit	Explains the absence of row order in relational tables
requires knobit	Designs a star schema for a stated grain
requires knobit	Designs a Data Vault model for auditable history
requires knobit	Designs a document structure for a stated access pattern
requires knobit	Designs views hiding physical structure from consumers
requires knobit	Recognises history kept without its constraints checked
schema:position	4

Used by

consists of	Data modelling