Sensitive data changes, kept before and after.
Tadpole History Hub records the before and after of data changes. Designate tables that hold sensitive data — ledgers, users, and more — and it automatically captures the authorization, reason, and before/after content of every change, then retains it.
Designate the table. Review. Keep before and after.
For tables holding sensitive data, write an INSERT, UPDATE, or DELETE, review the expected before/after data, and execute. The authorization, reason, and before/after values are recorded and retained automatically.
Every change,
on the record.
Require approval by operation type — INSERT, UPDATE, DELETE, DDL, and more — and designate approvers. Approved changes stay on record: who changed what, and when.
Queries and
migrations, safely.
Register a change by writing SQL directly or uploading a .sql file. A single query or a migration script — every change is recorded before and after, and managed safely.
Who, why, and
what changed.
On execution, the job number, reason, approver, and before/after content are recorded and retained — so you always have evidence of who changed what, and why.
Supported databases
Tadpole History Hub supports the following databases.
| # | Database | Supported version |
|---|---|---|
| 1 |  MySQL | 5.4.x or later |
| 2 |  MariaDB | 5.5.x or later |
| 3 |  PostgreSQL | 9.1.x or later |
| 4 |  Oracle | 10g or later |
Change evidence for every team
Evidence-ready change records
Every INSERT, UPDATE, and DELETE on a designated table is kept with its before and after values — ready as audit evidence.
Reason and approval on every change
Each change carries a job number, a description/reason, and an approval, linking it to who changed what and why.
Scoped to what matters
Designate only the sensitive tables — ledgers, users, and more. A WHERE clause is required, so changes stay deliberate.
Keep every change — before and after.
Compliance and DBA teams use Tadpole History Hub to record and retain the before/after of data changes on sensitive tables.