Conversion of Oracle to alternative relational databases


Conversion of Oracle to alternative relational databases follows a similar path irrespective of the choice of target database. Typically we would see migrations forming part of a larger project that includes a change in platform as well. In such cases a client may opt for a database which they associate with the target platform, such as SQL Server when Microsoft Windows is the target platform.
  • Database Conversion

    An Oracle migration will consider all the major elements inherent to the database, which will include the table and data definitions which means columns definitions, identity columns, integrity constraints, indexes, stored procedures functions and triggers. Once established, the following step in the migration is that of the data and here the volumes of data will dictate the strategy which must be employed. In addition if a change in character set is required, impacts on collating sequences must also be considered.

  • Conversion Process

    The conversion of databases follows a simple process. Firstly there is the conversion of the database definitions, secondly (and based on this) the generation of any scripts and processes that will be used to automate the migration of the data from the source to the target databases. Finally, there the question of ensuring that the process is automatic and repeatable and that it can be used for the migration of all testing and production data.