Joins sapd_reports_aspx_calls to the stored calls on incident number.
Stored calls are sapd_calls_live (active and just settled) and sapd_calls_history (everything older).
The incident span for each year is the first through last SAPD-YYYY-####### number in the reports table.
A stored row outside that span is from a part of the year the reports download did not cover, so it is left out of the missing-row counts.
The index is the seven digits after the year. SAPD-2026-0000100 followed by SAPD-2026-0000103 means indexes 0000101 and 0000102 have no row in that set.
Back to Reports import
Which table is missing rows
Report rows are counted once even when the same incident is in both stored tables. “Missing from stored calls” means the incident is in neither live nor history.
Year
Report rows
In live
In history
In both
Missing from stored calls
Run the comparison to load this table.
Stored rows inside the report incident span
These counts are live and history rows whose incident number falls between the first and last report incident for that year, and that the reports table does not have.
Year
First report incident
Last report incident
Live rows
Live missing from reports
History rows
History missing from reports
Run the comparison to load this table.
Missing incident indexes
Each jump from one stored incident to the next adds the indexes in between. Reports and stored calls are measured separately inside the same year.
Year
Set
Rows
First incident
Last incident
Index span
Missing indexes
Jumps
Largest jump
Run the comparison to load this table.
Largest jumps from one incident to the next
Set
Year
Previous incident
Next incident
Missing indexes between them
Run the comparison to load this table.
Report rows missing from stored calls
Incident
Category
Problem
Response
Address
—
Live rows in the span missing from reports
Incident
Problem
Call time
Address
—
History rows in the span missing from reports
Up to twelve of the newest missing history incidents for each recent year that has any.