Looking for a reliable and vigorous solution for migrating your database? Let's do it with us!
Seamless, secure migrations for your Teradata to Vertica transition
Stop losing time, avoid operational costs and optimize performance of your IT infrastructure by moving Teradata to Vertica with Ispirer.
Book a demoMigrate business logic to application layer to mitigate performance issues
Ispirer Toolkit automates the migration of sql objects to an app layer to the full. No manual rewriting required
Avoid inefficient allocation of resources with pre-migration services
Expert consulting and database audit prevent additional costs and help to optimize the migration roadmap
Choose turnkey migration services to focus on more important initiatives
Ispirer experts offer comprehensive migration services, delivering a ready-to-use database with minimal effort on your part. Smooth and efficient transition from point A to point B
Ispirer Toolkit automates the migration of database objects from Teradata to Vertica. Both conversion with connection to the source database, as well as conversion of files containing scripts are possible. Ispirer Toolkit supports migration of the following objects: tables, views, functions, procedures, sequences. As a result, each separate database object is converted to its equivalent in Vertica.
If you have your own applications, the Embedded SQL and Database APIs can be converted using either Ispirer Toolkit or Ispirer Service. As a result, they will be able to work with your new Vertica database.
Table and Data Conversion
Ispirer Toolkit converts tables with all related objects (indexes, referential integrity constraints) and data to the target Vertica database. All Teradata native data types are converted to the Vertica equivalent. If necessary, the user can change the default settings of data type mapping.
Procedure and Function Conversion
Teradata user procedures and functions are converted to UDxs in Java, which are used to deploy Vertica UDF. Each UDx type consists of two classes (one is nested in another). The nested class is the main one, it extends the ScalarFunction class and does the primary work (transformation, aggregation, etc.). The class usually has one method in which the actual work of the source function or procedure is performed. This class is named as the source procedure or function with the appended Factory. The second class is a singleton factory, it extends the ScalarFunctionFactory class. It defines one method that creates instances of the first class, and can define another method to manage parameters. It is named as the source function or procedure. Finally, Java UDx can be deployed to Vertica in the standard way.
Teradata built-in functions and procedures are converted to their equivalents in Java. If there are none, the tool converts them to the methods in a helper class in Java that emulate the same behavior, as well as work just like in the Teradata database.
Have questions about migration from Teradata to Vertica?