Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
15 results across 1 active filter
Page 1 of 1
Pre-aggregates two one-to-many relationships before joining them to prevent fanout from corrupting financial totals.
Builds several daily business metrics in one grouped query while keeping each metric definition explicit.
Combines daily aggregation, a calendar table, and a window frame to calculate true seven-calendar-day revenue.
Distinguishes instants, local calendar values, offsets, and named time zones so APIs and persistence survive daylight-saving and locale boundaries.
Builds a race-safe upsert around database-enforced identity, explicit conflict semantics, retries, ordering, and side-effect boundaries.
Protects transactional traffic from reporting load through freshness requirements, bounded asynchronous jobs, tuned summaries, workload isolation, replicas or warehouses, and explicit capacity gates.
Explains relational modeling, duplication, write consistency, read performance, and when denormalized data is justified.
Groups normalized email values to identify duplicates before adding or repairing a uniqueness rule.
Uses a recursive CTE to return hierarchy depth and a readable root-to-node path.
Shapes an API list from its contract and cardinality, projecting only required values while preserving authorization, stable pagination, bounded nesting, index support, and measurable query cost.
Explains referential integrity, cascade delete trade-offs, restrict behavior, soft deletes, and operational safety.
Explains aggregate queries, grouping keys, filters before and after aggregation, and business-count correctness.
Prevents lost updates with an original rowversion predicate, maps zero affected rows to an explicit conflict, and defines user, retry, aggregate, and API precondition behavior.
Makes business uniqueness race-safe with the exact database key, while handling normalization, tenant scope, nulls, soft deletion, rollout cleanup, and stable API conflicts.
Uses ROW_NUMBER with deterministic partition ordering to return one complete latest row per group, then evaluates index support, tie semantics, scale, and read-model alternatives.