Commit to explicitly separating normalized source/core models from dimensional serving models on one active initiative.
An active analytics initiative that currently pulls from operational tables or raw replicas Use this where people keep debating whether to query the source directly or where metric definitions are drifting with app schema changes. For [project], I will name the normalized source/core tables, name the dimensional serving tables, and document which business questions each layer is responsible for. A new dashboard or mart is being built directly from replicated application tables and no one has written what the serving model will be. Engineers and analysts are debating whether a new metric should live in the source model or in…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in