Solution Overview — For Management
Every migration eventually needs one person to accept the risk of cutover. That decision is only as good as the evidence behind it, and most projects reach that point with far less evidence than anyone would like to admit — a sample of manually-checked queries, and a lot of confidence built on hope.
Oninit® DBReplay replaces that with a statement-by-statement, row-by-row account of the real captured production workload, replayed against the migrated target and compared against what the source actually returned. The decision-maker gets evidence instead of a sample.
The business case
| Outcome | How DBReplay delivers it |
|---|---|
| Lower cutover risk | The full captured workload is proven against the target before cutover, not discovered to be broken during it. |
| No live-source security review to stall the project | DBReplay never connects to the live source system. Everything derives from artefacts your team produces. |
| Performance risk known in advance | A statement-level comparison of the target's performance against the source's, at production concurrency, before go-live. |
| A clean decision boundary | DBReplay asserts what is technically provable and reports it in full. Acceptance stays a business decision, made with evidence rather than instead of it. |
| Value beyond the one-off proof | The same capture, replayed against different target configurations, becomes a sizing instrument — often worth more to the customer than the original migration proof. |
What it removes from the risk register
- “We won't know if the migration actually worked until real traffic hits it.”
- “Security won't sign off on a tool that needs a live connection to the mainframe.”
- “We tested the queries we thought of, not the ones that actually run in production.”
- “Nobody can tell us in advance whether the new system will be faster or slower.”
Why Oninit
DBReplay is delivered by the same Oninit engineering team behind DBVoyeur, Oninit’s SQL-level performance monitor, and two decades of supporting the global Informix community as “the Down System Specialists.” This is a team that already reads production database traffic at the wire level for a living — DBReplay turns that capability toward proving a migration rather than diagnosing an incident.
Delivery model
Sold as a product with consulting attached, licensed per migration project. Rules and the underlying tooling are cross-project assets that compound with experience; your artefacts and configuration stay isolated to your engagement.
Time to value
| Step | Typical effort |
|---|---|
| Trial capture | This week — a plain packet capture, no DBReplay software involved, no unusual security approval. |
| Coverage report from the real captured workload | Early in the engagement, before any replay runs — the first concrete evidence of how much of the workload is straightforward. |
| First full replay-and-compare run | Depends on catalog extract and target provisioning, which sit outside DBReplay's own control. |
| Signed migration-readiness report | The artefact the cutover decision rests on. |
Next step
A short scoping call to understand the migration and the risk it needs to retire. Call +1 913 732 8892 (US) or +44 20 8133 7529 (UK), or email support.info@oninit.com.