# Historical reads

Check availability and retention before relying on historical query results.

Source: https://particledb.ai/sql/time-travel/

Historical queries require a server configuration that explicitly supports them. Ordinary durability and transaction isolation do not imply that older versions are queryable.

## Before using historical queries

Check the installed server's `start --help` for time-travel options. Verify retention, timestamp format, schema-change behavior and persistence across restarts using your release.

A historical query must fail clearly when the requested history is unavailable. Do not treat an empty result as proof that no records existed at that time.

## Alternatives

For application audit history, maintain explicit event or change records with stable identifiers and timestamps. Keep that design separate from the database's crash-recovery mechanism.

[Transactions](/sql/transactions/) · [Durability](/operations/durability/) · [Feature availability](/reference/limits/)

## Related

[Documentation home](/docs/) · [Troubleshooting](/guides/troubleshooting/)
