DBVoyeur and DBReplay
DBVoyeur tells you what your database is doing, continuously. DBReplay tells you whether a different database would do the same thing with the same work. Two different questions, built on the same passive-capture foundation.
Start with the question you're asking
DBVoyeur
Where is time going in this database, right now and over time? A permanent, non-intrusive SQL performance monitor for one live system.
Explore DBVoyeur →DBReplay
Does a migration target produce the same dataset, and how does it perform, under real production load? A project-scoped capture, replay and comparison exercise.
Explore DBReplay →Two different questions
| DBVoyeur | DBReplay | |
|---|---|---|
| Question answered | Where is time going in this database, right now and over time? | Does the target produce the same dataset, and how does it perform, under the captured production load? |
| Mode | Continuous monitoring of one live system. | Project-scoped exercise: capture once, replay many times. |
| Lifecycle | Permanent install. Runs for as long as the database does. | Runs for the duration of the migration project, then comes out. |
| Databases involved | One, live. | Two — a captured source and a target instance under test, which can be different database vendors entirely. |
| Touches the database | Never. Passive observation of traffic only — it issues no SQL. | Yes. Executes captured production SQL, writes included, against a real target. |
| Output | Live dashboards and trend views in the browser. | Replay verdict and a signed report: dataset equivalence, performance comparison, run-to-run comparison. |
| Licensing | Per monitored instance, tiered. | Per migration project, product plus consulting. |
Capture is the same for both
Getting the traffic is one proven mechanism, shared by both products. The products diverge only in what they do with it afterwards — libpcap on the monitored host or a network tap, a client-side capture where TLS 1.3 rules out reading the wire, or a mainframe platform-level clear-text trace for z/OS sources.
DBVoyeur scopes what DBReplay should capture
DBVoyeur on the source system answers the question DBReplay has to ask first: which window is worth capturing? Peak versus mean, statement mix, connection churn and transaction rate are exactly what DBVoyeur already measures, and exactly what sizes a capture. A customer already running DBVoyeur arrives at a migration with the scoping evidence already in hand.
Not sure which one fits?
A short scoping call settles it quickly.
Talk to an expert →