New: Cookbooks and AI ExplanationsStep-by-Step recipes to solve problems connected to Roadmaps and Cheat Sheets. Need more details? Use AI buttons for structured and simple explanations with concrete examples throughout the whole platform.Take a look
Somebody asked if the load actually got everything, and all you had was a guess.
What you'll have at the end
A reconciliation report showing the source count next to the loaded count for every run
You need
A load that already moves rows from a source table into a target table on its own schedule, with the ability to run a query against both sides whenever needed.
Not covered
Fixing why rows went missing, landed twice, or changed value in the first place, or stopping a bad batch before it reaches a report; this recipe only proves, after the fact, exactly what did and did not make it across correctly, for any run someone asks about.
Leans on
Give every load a data quality gate
use that one to stop an obviously bad batch before it reaches a report; this recipe is for proving what actually happened afterward, across many runs.
Make a pipeline safe to rerun with an upsert
reach for this once the missing or extra ids trace back to a crashed rerun, so the load itself stops producing the gap instead of only reporting it.
Checked 25 Aug 2026
Part of the ETL (Extract, Transform, Load) cookbook