Database Migrations

Challenges

Obsolescence factors as well as skills shortage and high cost of ownership of pre-relational databases drive the need for their replacement. Converting pre-relational databases to SQL standards, or consolidating heterogeneous and multiple data formats, is the best way to reach the following objectives:

  • Reduction of DBMS cost of ownership
  • Implementation of an open and durable relational database allowing in particular the freeing of corporate data and to make it easily accessible to the rest of the information system
  • Reduction of application asset maintenance costs by simplifying data access upgrades



Requirements

Projects eliminating pre-relational databases must meet the following requirements

  • Keep response times to a minimum
  • Minimize system resource usage relative to the pre-relational database
  • Maintain the behavior and features of existing applications
  • Preserve code maintainability after conversion, for future upgrades



Solution

Metaware’s migration process covers all necessary steps of a database replacement i.e., data discovery, qualification, target schema generation, reloading and static testing, modifications to impacted programs.



Refine supports many proprietary data formats, including:


File systems
(sequential, relative, indexed)
ESDS, KSDS... ENSCRIBE, ISAM, UFAS, QSAM, SAM, SFS, VSAM, GDG, PDS, …
Pre-relational databases ADABAS, DATACOM, DMSII, CA-IDMS, IDMS-X, IDSII, IMAGE, IMS/DB (DL/1), ...
Relational databases DB2, INFORMIX, nonStop SQL, ORACLE, RDB, SQL Server, SYBASE, …

Refine can generate database migrations for the majority of today’s RDBMS, including DB2, ORACLE, and SQL Server.




Benefits

Complete automation allows the project to focus on schema, path and constraints optimization, through several iterations. Metaware’s solution proposes many data rationalization and improvement options for a wide array of technical situations.

Need more information on Metaware’s database migration solutions? •••