The migration process is data exchange between databases in same or different formats. For example, the corporate information system migrates from PostgreSQL to Oracle. The data and, probably, structure transformation to the new format is data migration. In the example, it is a single process. But a few cases require scheduled migration. In most cases it is joining data from external system to the main database or joining a few databases to one for analytical purposes.
DTM Migration Kit was designed and developed for complex automation tasks. It allows users to combine a few different rules in the single job. For example, the user can define a sequence of transformation steps with external program execution (like "sendmail") if any error happens. Of course, the created job (also known as "project") can be executed under schedule. The migration kit provides users with the related interface.
The key DTM Migration Kit difference is multivendor environment support. It can migrate data from Oracle to SQL Server, from Informix to MySQL, from Interbase to IBM DB2, etc. To provide this feature the program uses common database interfaces: ODBC, OLE DB, and BDE/IDAPI. These interfaces with drivers of providers cover all database multiplicity.
For database migration, the software offers three modes: single table, all tables or list of tables assigned by the user. Another source of the migration process is database query (SQL statement). It is a useful option if two or more tables should be joined to the single object at the target side. For the single, table the migration tool allows the user to enter WHERE clause to limit rows to be migrated as well as select columns for.
The program can migrate all, new or changed rows. It is a good way to optimize database and channel loading if you need to synchronize database status only.
Different databases have different sets of data types with possible compatibility problems. To avoid that the migration kit has "data type mapping" feature. This function allows users to associate data types in source and target databases if DTM Migration Kit could not do that automatically.