Performance considerations

Performance of SQL Tran

When selecting a region where your want SQL Tran deployed, select the region closest to your users, to minimize network latency.

If you have users that are geographically dispersed, you may want to deploy multiple instances of SQL Tran to improve the user experience.

Parsing, analysis and transpilation speed linearly increases with CPU cores as our engine is parallelizable and multi-threaded. Basic plan comes with 4 CPU cores, while Pro and BYOL plans come with 8 CPU cores. This means that most operations in Pro and BYOL plans are twice as fast compared to the Basic plan.

Performance of translated code

SQL Tran will follow best practices when translating the code and generate as idiomatic code as possible.

Still, it is important to keep track of the performance to know which areas, due to different architectures of target database compared to the source, might require special attention and possible manual rewrite. For this reason, all tests in SQL Tran automatically provide performance comparison between source and target. Time required to execute a specific procedure or function, as well as time it took for a view to return its data will be reported.