Oracle to MySQL Migration

 

Copyright © 1999-2012. Ispirer Systems Ltd. All Rights Reserved. 3
An Oracle to MySQL migration can be a very challenging process, particularly if Oracle
specific features are in use, such as the ones described above.
However, such a migration could be relatively easy and risk-free. Such would be the case if
the target database contained a relatively small amount of tables and simple business logic.
Since cost and risk may vary from project to project, it is important to fulfill a preliminary
assessment.
Assessment
The purpose of the assessment is to define the scope, feasibility, cost and risk associated in
migrating from an Oracle database to a MySQL based database implementation.
Database Assessment
Firstly, you need to define the types of database objects and how many of them you will
need to migrate. Objects are items such as the following:
• Tables
• Views
• Procedures
• Functions
• Packages
• Triggers
• Sequences, synonyms etc.
If you need to convert PL/SQL code (procedures, packages, functions and triggers) or
view/queries containing Oracle specific SQL syntax, you have to investigate what features
are used and define the number of their occurrences. Examples of items that need to be
accounted for are:
• Non-ANSI compatible SQL functions, operators and statements
• Results sets
• Cursor loops
• Exceptions
• Temp tables
• Object types and functions
• Collections
Copyright © 1999-2012. Ispirer Systems Ltd. All Rights Reserved. 4
• Dynamic SQL
• Built-in packages
• OLAP functions
• XML functions etc.
After you have finished the examination, it is best to select MySQL equivalents or solutions
to replace Oracle specific functionality. You can find typical solutions in subsequent
chapters.

 

File Download