Demo presentation text:
This is a demo about the migration tools provided by Ispirer Systems for the MySQL to Oracle migration.
First of all I’d like to mention that Ispirer Systems provides tools and services for automating the databases and applications migration processes for a variety of conversion directions. The list of tools supplied for such kind of automation is as follows:
• Sqlways.exe – a command line tool that can be run in batch mode and can perform the automatic conversion of the database using the ODBC connection or the database and application code provided in scripts.
• SQLWays Wizard – a GUI tool that is designed to simplify the database conversion process tuning for the sqlways command-line tool. Works with the source database using the ODBC connection.
• SQLWays Studio – a GUI tool that is designed to simplify the database or application script conversion process tuning for the sqlways command-line tool. Works with one script at a time.
• SQLWays Commander - a GUI tool that is designed to simplify the database or application scripts conversion process tuning for the sqlways command-line tool. Works with several scripts at a time.
In this demo, I will show you the MySQL to Oracle migration using SQLWays Wizard, SQLWays Studio and SQLWays Commander Tools mentioned in the list provided.
First let’s start from the SQLWays Wizard.
This tool can connect to MySQL database using the ODBC connection only. So, to migrate from MySQL to Oracle, you need to provide the ODBC DSN for MySQL on the “Choose a Source Database” page. Also you need to specify a user and a password with the appropriate rights for making selection from systems tables from MySQL.
On a “Choose a Target Database” page you need to choose the target database from the list of the supported databases. As you can see the Oracle database is specified here. Also you need to provide other credentials for the Oracle database for a support of definitions and data load using native utilities of this database.
All the objects that SQLWays manages to extract from the MySQL database are represented in a tree view on the “Specify Database Objects or Query” page. Here you can select all the objects required for the migration.
After that you can specify different options for automated MySQL to Oracle conversion, like option that controls the schema name conversion, reserved words conversion, data types conversion, identifier names conversion and etc. Also there are options that can help you to run the definitions and data migration in separate processes.
On the “Specify Export File Options” page you need to provide the directory, which serves as an intermediate repository for the whole migration process and stores all the automatically generated files, like SQL files with the converted definitions of the objects, TEXT files with the data prepared to be loaded into the target database, BAT or SH files with the commands for native utilities to load both definitions and data on Windows or on Unix like OS.
Control files with the load data command for the SQL loader tool to load the data into the Oracle database.
All the MySQL to Oracle migration process is performed in two steps. Each of them has separate logging information.
For the Export process sqlways.log files are generated with the information about the: objects read from the MySQL database, their number, number of rows of data and size of the data per each table extracted, number of lines of code (LOC) per each business logics objects, like views, synonyms, stored procedures, functions, triggers, packages and etc. At the end of the export log file you can find summary information per each object type regarding the number of objects, common size of data, number of rows of data or lines of code, depending on the object type, export status and issues if there are any and the Total information for the whole database export.
Similar information but in more readable format is provided in the sqlways_report.html file. There is a summary table with the complete export status and statistics per each object type and there are also tables with the list of objects and more detailed statistics for each object extracted from MySQL database.
As for the import process, SQLWays generates a sqlways_imp.log file for the import into the Oracle database that contains information about objects that were loaded and issues during the import process if there are any.
Now let’s turn to the SQLWays Studio and SQLWays Commander tools that are designed for database scripts and application scripts conversion purposes.
To convert MySQL to Oracle with SQLWays Studio all you need to do is to provide the conversion direction using the “Source” and “Target” options, after that place the source MySQL code to the right pane of the tool and Run the conversion. At the bottom of the tool you can see the log of the conversion process that shows if there are any errors during the script conversion from MySQL to Oracle database. Once the conversion has been completed, you can compare both source and target scripts in one tool side-by-side for your convenience.
In SQLWays Commander there are also two panes that give the opportunity to specify the file or files or the whole directory for the conversion. So, to convert from MySQL to Oracle you just need to specify the source and target from the list of supported databases, specify the files for conversion and click Run. When you specify the directory for the conversion, you also need to provide the template for the files that you would like to convert from MySQL to Oracle database and provide the target directory for the conversion results. At the bottom, there is generated conversion log file with the information about conversion issues if there are any. After the conversion by double-clicking the file in the source and in the target pane you can review the conversion results side-by-side like in SQLWays Studio.
That’s all I wanted to tell you in this Demo. The information about the peculiarities of MySQL to Oracle migration and other tool that Ispirer Systems provides for database migration support will be described in our next Demos or can be found on our website. I hope this Demo was useful. Thank you! Bye