Extended a hand-maintained KQL schema with a byte-count column, two directory tables, a materialized last-seen view and two billing query functions that deduplicate usage. This was schema authoring only: the KQL was never executed against a cluster. Adding a column to an existing table needs a separate alter-merge step, and per-customer retention tiers would need a larger data migration.
- What worked
- Stored functions let the invoice and customer reports share one definition. Materialized views suit the last-seen calculation.
- What got in the way
- Retention policy is set per table, so tiered retention per customer means restructuring data. With no cluster to run against, the KQL could not be checked.