Database
Schema and dependencies
Fewer objects, one home for each fact, and a model a new engineer or agent can read.
- Which database objects no longer earn their keep?PromptThe list of views, functions and triggers has grown hard to reason about.
- Are we storing the same truth multiple times?PromptCaches, aggregates, materialized views or derived columns drift from the raw facts.
- Can the schema be easier to understand without losing depth?PromptNew developers or agents keep misunderstanding names, concepts or relationships.