Correct and fast.
Every correctness test in SQL Tran also measures execution time. You know not just that your code is correct, but that it performs.
A migration can be functionally perfect and still fail in production if the translated code runs slower than the original. Performance regressions are one of the most common, and most dangerous, surprises after a database migration.
SQL Tran eliminates the surprise. Performance measurement is built into every test, not a separate step. Every time you validate correctness, you also get a clear picture of how execution time compares between source and target.
How it works
Built into every test, not bolted on
Performance testing in SQL Tran is not a separate mode or a different kind of test. It is an additional dimension of every correctness test. When SQL Tran runs a test against both databases, it records execution time for each side. The result UI displays match status, record counts, and timing data, all in one view.
By the time you have validated correctness across your database, you already have a complete performance profile for every tested object. No extra configuration, no extra test runs, no separate tooling.
What it measures
Timing across every object type
Tables
Time to read and return all rows from source vs. target. Identifies tables where data retrieval performance differs significantly.
Views
Query execution time on source vs. target. Reveals views where the target engine's query plan diverges from the source.
Procedures
Full execution time including all side effects. Captures the total cost of procedure execution, not just the return value.
Functions
Execution time for return value computation. Flags functions where the translated implementation takes measurably longer.
Early warning system
By catching performance regressions during testing, not after go-live, you have time to investigate and address them. Whether the issue is a missing index, a suboptimal emulation, or a fundamental difference in how the target engine processes a query pattern, you will know about it before it affects production workloads.
Interpreting results
Timing in context
Performance comparisons are most meaningful when source and target databases contain the same data. SQL Tran shows timing alongside record counts so you can distinguish genuine performance differences from results skewed by data volume mismatches.
For example, if a table returns 27 records from the source in 5ms but returns 0 records from the target in 1ms, the timing difference is not meaningful. The correctness mismatch is the real issue. SQL Tran surfaces both dimensions together so you can read results in context.
Key benefits
- Performance measurement built into every correctness test. No extra step.
- Execution time recorded and displayed for both source and target
- Results shown alongside record counts for proper context
- Catches performance regressions before go-live
- No separate tooling or configuration required
Validate correctness and performance in one pass
Every test you run already includes performance data. No extra steps. No extra tools.