# Check report data after a restart

Coordinator DB has no refreshable materialized-view scheduler to resume after a restart. An ordinary persistent view retains a SELECT definition, while a persistent report table retains the rows that were committed to it. These objects have different freshness rules.

After restarting, connect to the intended named database and read the view with a known predicate. The result is calculated from the current source data. There is no saved refresh interval or pending view refresh to inspect.

For a manually maintained report table, compare its contents with the source calculation:

```sql
SELECT count(*) AS source_rows, sum(amount) AS source_amount
FROM report_source;

SELECT count(*) AS report_rows, sum(amount) AS report_amount
FROM saved_report;
```

Replace these example object names with the tables used by your application. Compare like-for-like filters and aggregation levels; equal row counts alone do not prove equal contents. Record a completed refresh marker in the application's own data if its readers need an explicit freshness signal.

Uncommitted transaction work is not a successful refresh. Keep refresh changes and their marker in the same committed transaction when they must remain consistent.

See [views](https://coordinatordb.com/docs/reference/statements/create/view) and [transactions](https://coordinatordb.com/docs/concepts/features/operations/insert/transactions).