DATADrone4 is not simply a tool designed for migrating database schemas and data from one engine type to another. Rather, it is a methodology, which includes tools, testing methods, project management, implementation, and user participation resulting in not only a database migration, but an application migration and successful deployment. This methodology is copy written and can be employed by Old American, Inc. and our contracted partners.
DATADrone4 has been designed from the inception to fulfill the purpose of simplifying database migrations from any supported source database engine (Oracle, Informix Dynamic Server, DB2 UDB, SQL Server, or Sybase) to any supported target database engine eliminating from 90% to 95% of the manual effort normally contributed by the organization’s technical staff. Thus, shortening the duration required to perform such a major effort to an acceptable time frame. Our objective is to complete the project in no more time than is necessary to achieve success. Additionally, in the conditions of 24x7 OLTP environments the migration can take place in parallel with normal operations; cutting to live operation in the new environment after an intensive simultaneous testing and acceptance process.
DATADrone4 is comprised several distinct modules. The initial module is responsible for the actual migration of the data and Meta data from the source to the target. This is accomplished by first converting the schemas from source system specific SQL to a proprietary data object, and then by converting it from this object into the target system specific SQL for the new database instance. It is important that this approach is taken as it then allows DATADrone4 to support more complex environments and to provide flexible operations and improved security measures that are required of today’s demanding environments.
The DATADrone4 method is responsible for and capable of converting source code (scripts and programs) so that it connects to the new database instance, functions properly with the new database, and cleanly operates in the new database instance.
Different pluggable modules for different types of original system constructions, source code, and scripting languages are employed to accomplish the challenge of diversity from site to site and even from application to application within a site location.