Write a reproducible workload result ​

A useful workload report explains a concrete reader task, the query change and the evidence that its result remained correct. Use a synthetic or shareable dataset so another person can repeat the comparison. Do not invent customer names, private deployment figures or gains that were never measured.

Describe the input schema, relevant value distribution and expected output. For a lookup improvement, record the predicate and selected access plan before and after the index change. For a report rewrite, compare results in both directions and account for duplicate counts when they matter.

Keep measurement conditions consistent: same data, parameters, output format, result caps and connection mode. Report several representative observations when timing varies. Query IDs connect those observations with terminal duration, read work and memory counters in the query log.

State the practical boundary of the evidence. A faster lookup on one dataset does not establish a universal performance claim, and a smaller response can improve delivery without reducing all SQL work. Share only public SQL behavior and sanitized examples.

See result comparisons, query measurements and query history.